is it possible to authorize only selected users to use eclipse-che dashboard website?

[Divine1]

Summary

i have installed eclipse-che in k8s cluster. i have used dex as the OIDC provider and i have integrated dex with my organization's gitlab login.

currently anyusers who has access to the my organization's gitlab login credentials are able to use the eclipse-che dashboard webpage after successful authentication/authorization via dex-gitlab.

i dont want to allow access to all the users who has access to myorganization's gitlab to use eclipse-che dashboard webpage

Please let me know how to restrict/blacklist/whitelist users from using the eclipse-che dashboard?

Relevant information

No response

[tolusha]

/cc @sparkoo @karatkep
Do you know if it is possible? Have you ever faced such an issue?

[karatkep]

I think there is only one way to restrict access to Che - restrict access to k8s api server for the user... пт, 8 июл. 2022 г., 11:34 Anatolii Bazko ***@***.***>:

…

/cc @sparkoo <https://github.com/sparkoo> @karatkep <https://github.com/karatkep> Do you know if it is possible? Have you ever faced such an issue? — Reply to this email directly, view it on GitHub <#21539 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/APGFNMGJP2JRXKDR4NE6O23VS7RZRANCNFSM5273VZXA> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[Divine1]

@tolusha @karatkep

i have installed eclipse-che in k8s cluster. i have used dex as the OIDC provider and i have integrated dex with my organization's gitlab login.

is there any feature that can be used to blacklist/whistelist/restrict user access before redirecting to eclipse-che dashboard page after successful login in dex-gitlab?

[sparkoo]

I don't think there's currently clean way how to do that. You can maybe update rolebinding in user's namespace, removing permissions to Che resources. But I'm not sure it won't be reconciled back. Also new users will still be able to login to Che. I don't think there was ever such requirement.

[che-bot]

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.