Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Can not revoke Authorization - OAuth token for user was not found #22776

Closed
ibuziuk opened this issue Jan 19, 2024 · 4 comments · Fixed by eclipse-che/che-server#652
Closed
Assignees
Labels
area/che-server area/dashboard kind/bug Outline of a bug - must adhere to the bug report template. severity/P1 Has a major impact to usage or development of the system. sprint/current

Comments

@ibuziuk
Copy link
Member

ibuziuk commented Jan 19, 2024

Describe the bug

Can not revoke Authorization - OAuth token for user was not found

Che version

7.80@latest

Steps to reproduce

Screenshot 2024-01-19 at 12 58 29

Expected behavior

Authhorization is revoked without errors

Runtime

OpenShift

Screenshots

No response

Installation method

OperatorHub

Environment

Amazon

Eclipse Che Logs

No response

Additional context

No response

@ibuziuk ibuziuk added kind/bug Outline of a bug - must adhere to the bug report template. area/dashboard severity/P1 Has a major impact to usage or development of the system. sprint/next labels Jan 19, 2024
@akurinnoy akurinnoy self-assigned this Jan 19, 2024
@akurinnoy
Copy link
Contributor

From what I see, the dashboard works as expected. It uses the che-server API to revoke tokens for the selected provider. Thus, the dashboard does nothing with OAuth tokens.

Screenshot 2024-01-19 at 15 17 37

@ibuziuk
Copy link
Member Author

ibuziuk commented Jan 22, 2024

@vinokurig could you please take a look ?

@ibuziuk
Copy link
Member Author

ibuziuk commented Jan 23, 2024

@vinokurig please, take a look at the screencast since I'm not sure PR is addressing the issue I'm facing:

Screen.Recording.2024-01-19.at.13.45.50.mov

@vinokurig
Copy link
Contributor

@ibuziuk
I managed to reproduce the issue only with specific conditions:

  1. Go to the GitServices tab and see that the authorisation has the green icon which means that it is authorised.
  2. Open a new browser tab and manually revoke the authorisation in the GitHub authorised applications settings page.
  3. Switch back to the dashboard tab and revoke the authorisation.

See: the error appears but it is fixed with the PR.
Did you use another use-case to reproduce the bug?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/che-server area/dashboard kind/bug Outline of a bug - must adhere to the bug report template. severity/P1 Has a major impact to usage or development of the system. sprint/current
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants