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

Authorize only selected users to use eclipse-che dashboard website #21797

Closed
LiJunBJZhu opened this issue Nov 1, 2022 · 2 comments
Closed

Authorize only selected users to use eclipse-che dashboard website #21797

LiJunBJZhu opened this issue Nov 1, 2022 · 2 comments
Labels
area/install Issues related to installation, including offline/air gap and initial setup kind/enhancement A feature request - must adhere to the feature request template. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. severity/P2 Has a minor but important impact to the usage or development of the system.

Comments

@LiJunBJZhu
Copy link

Is your enhancement related to a problem? Please describe

My openshift cluster has more than one identity providers configured. Now all Openshift users, even who haven't been bind any roles, from any identity provider can access the Eclipse-che dashboard and start new workspaces. That costs much CPU/Memory resource of the cluster.

I only want to allow the users imported from one designated identity provider, or selected users, to access Eclipse che and start new workspace.

Describe the solution you'd like

Provide a feature that can be used to blacklist/whistelist/restrict Openshift user access before redirecting to eclipse-che dashboard page after successful login in Openshift.

Describe alternatives you've considered

#21539

Additional context

No response
@LiJunBJZhu LiJunBJZhu added the kind/enhancement A feature request - must adhere to the feature request template. label Nov 1, 2022
@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 Nov 1, 2022
@LiJunBJZhu
Copy link
Author

Find a similar request here #21539

@dkwon17 dkwon17 added severity/P2 Has a minor but important impact to the usage or development of the system. area/install Issues related to installation, including offline/air gap and initial setup and removed status/need-triage An issue that needs to be prioritized by the curator responsible for the triage. See https://github. labels Nov 1, 2022
@che-bot
Copy link
Contributor

che-bot commented Apr 30, 2023

Issues go stale after 180 days of inactivity. lifecycle/stale issues rot after an additional 7 days of inactivity and eventually close.

Mark the issue as fresh with /remove-lifecycle stale in a new comment.

If this issue is safe to close now please do so.

Moderators: Add lifecycle/frozen label to avoid stale mode.

@che-bot che-bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Apr 30, 2023
@che-bot che-bot closed this as completed May 7, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
area/install Issues related to installation, including offline/air gap and initial setup kind/enhancement A feature request - must adhere to the feature request template. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. severity/P2 Has a minor but important impact to the usage or development of the system.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@LiJunBJZhu @che-bot @dkwon17