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

Study: is it possible to use additional fields from Keycloak as a placeholder for k8s namespace #17570

Closed
skabashnyuk opened this issue Aug 5, 2020 · 1 comment
Closed

Study: is it possible to use additional fields from Keycloak as a placeholder for k8s namespace #17570

skabashnyuk opened this issue Aug 5, 2020 · 1 comment
Labels
area/che-server kind/task Internal things, technical debt, and to-do tasks to be performed. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale.

Comments

@skabashnyuk
Copy link
Contributor

Is your task related to a problem? Please describe.

Username may not be always compatible with k8s object names #15323

Describe the solution you'd like

The idea is to provide admins/users an instrument based on Kyecloak to set up their preferences
of what k8s namespace should be used for the workspaces. Potentially it can be an extra field in JWT token or some API method that can give this information by userid.

Describe alternatives you've considered

n/a

Additional context

n/a
@skabashnyuk skabashnyuk added the kind/task Internal things, technical debt, and to-do tasks to be performed. label Aug 5, 2020
@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 Aug 5, 2020
@nwalens nwalens mentioned this issue Aug 5, 2020
Closed
4 tasks
@skabashnyuk skabashnyuk added team/platform area/che-server and removed status/need-triage An issue that needs to be prioritized by the curator responsible for the triage. See https://github. labels Aug 5, 2020
@che-bot
Copy link
Contributor

che-bot commented Feb 4, 2021

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 Feb 4, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
area/che-server kind/task Internal things, technical debt, and to-do tasks to be performed. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@skabashnyuk @che-bot