che
che copied to clipboard
Revoke git service action is available after apply
Describe the bug
It is possible to execute the revoke git service action after its actual execution.
Che version
7.80@latest
Steps to reproduce
- Setup GitHub oauth: https://eclipse.dev/che/docs/stable/administration-guide/configuring-oauth-2-for-github
- Start a workspace from a GitHub repository, accept the GitHub token agreement.
- Go to the dashboard
Git Services
tab and revoke the GitHub authorisation. - Quickly go to the
Personal Access Tokens
tab and then quickly switch back to theGit Services
tab. - See: the GitHub still has an authorised state as the provision request was ignored and the related oauth token was not deleted.
- Revoke the GitHub authorisation.
- See: a notification about successful revoke appears and the authorisation status is changed to unauthorised.
Expected behavior
The git service must be in the unauthorised state and the revoke action must be always inactive after revoking.
Runtime
OpenShift
Screenshots
No response
Installation method
chectl/latest
Environment
macOS
Eclipse Che Logs
No response
Additional context
No response