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.

Sign up for GitHub

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

Jump to bottom

Add a warning widget near provider's name if we don't have an ability to revoke automatically #22039

Closed
olexii4 opened this issue Mar 6, 2023 · 1 comment · Fixed by eclipse-che/che-dashboard#765
Closed

Add a warning widget near provider's name if we don't have an ability to revoke automatically #22039

olexii4 opened this issue Mar 6, 2023 · 1 comment · Fixed by eclipse-che/che-dashboard#765
Assignees
@olexii4
Labels
area/dashboard kind/enhancement A feature request - must adhere to the feature request template. new&noteworthy For new and/or noteworthy issues that deserve a blog post, new docs, or emphasis in release notes severity/P1 Has a major impact to usage or development of the system. sprint/current team/A This team is responsible for the Che Operator and all its operands as well as chectl and Hosted Che
Milestone
7.64

Comments

@olexii4
Copy link
Contributor

olexii4 commented Mar 6, 2023

Is your enhancement related to a problem? Please describe

Nowadays we support automatic revoke for GitHub only because we do not have the needed API for other providers. So, revoking procedure should be done manually for all other providers instead of GitHub.

Describe the solution you'd like

I would like to have a warning widget near the provider's name if we don't have the ability to revoke it automatically. This warning message should have a popup with a detailed explanation of the problem.

Describe alternatives you've considered

No response

Additional context

No response
@olexii4 olexii4 added kind/enhancement A feature request - must adhere to the feature request template. area/dashboard labels Mar 6, 2023
@che-bot che-bot added the status/need-triage An issue that needs to be prioritized by the curator responsible for the triage. See https://github. label Mar 6, 2023
@ibuziuk ibuziuk mentioned this issue Mar 6, 2023
Closed
45 tasks
@ibuziuk ibuziuk added severity/P1 Has a major impact to usage or development of the system. sprint/next team/A This team is responsible for the Che Operator and all its operands as well as chectl and Hosted Che sprint/current and removed sprint/next status/need-triage An issue that needs to be prioritized by the curator responsible for the triage. See https://github. labels Mar 6, 2023
@ibuziuk ibuziuk mentioned this issue Mar 17, 2023
Closed
50 tasks
@olexii4 olexii4 self-assigned this Mar 23, 2023
@olexii4 olexii4 mentioned this issue Mar 31, 2023
Merged
@l0rd l0rd added the new&noteworthy For new and/or noteworthy issues that deserve a blog post, new docs, or emphasis in release notes label Apr 6, 2023
@l0rd l0rd added this to the 7.64 milestone Apr 6, 2023
@devstudio-release
Copy link

sync'd to Red Hat JIRA https://issues.redhat.com/browse/CRW-4188

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@olexii4 olexii4

Labels
area/dashboard kind/enhancement A feature request - must adhere to the feature request template. new&noteworthy For new and/or noteworthy issues that deserve a blog post, new docs, or emphasis in release notes severity/P1 Has a major impact to usage or development of the system. sprint/current team/A This team is responsible for the Che Operator and all its operands as well as chectl and Hosted Che
Projects
None yet
Milestone
7.64
Development

Successfully merging a pull request may close this issue.

Add a warning widget if API does not support the automatic token revoke eclipse-che/che-dashboard
5 participants
@l0rd @ibuziuk @olexii4 @devstudio-release @che-bot