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

Provide some meaningful error message during user manipulation operation in case if Che is configured to work with Keycloak #9015

Closed
skabashnyuk opened this issue Mar 5, 2018 · 0 comments
Closed

Provide some meaningful error message during user manipulation operation in case if Che is configured to work with Keycloak #9015

skabashnyuk opened this issue Mar 5, 2018 · 0 comments
Labels
kind/task Internal things, technical debt, and to-do tasks to be performed.

Comments

@skabashnyuk
Copy link
Contributor

skabashnyuk commented Mar 5, 2018 •
edited
Loading

Description

When Che is configured to work with Keycloak user can be created only on the first user connection to che from information provide by keycloak's JWT token. Also, some part of profile data is also taken from Keycloak. That means that some operation like user creation, removal, profile update has no sense and has to be made in keycloak first.

Related issue #9009
@skabashnyuk skabashnyuk added status/open-for-dev An issue has had its specification reviewed and confirmed. Waiting for an engineer to take it. kind/task Internal things, technical debt, and to-do tasks to be performed. team/platform labels Mar 5, 2018
@skabashnyuk skabashnyuk mentioned this issue Mar 5, 2018
Closed
12 tasks
@benoitf benoitf changed the title Provide some meneful error message during user manipulation operation in case if Che is configured to work with Keycloak Provide some meaningful error message during user manipulation operation in case if Che is configured to work with Keycloak Mar 7, 2018
@skabashnyuk skabashnyuk mentioned this issue Mar 23, 2018
Closed
9 tasks
@mkuznyetsov mkuznyetsov mentioned this issue Mar 26, 2018
Merged
@mkuznyetsov mkuznyetsov removed the status/open-for-dev An issue has had its specification reviewed and confirmed. Waiting for an engineer to take it. label Mar 30, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
kind/task Internal things, technical debt, and to-do tasks to be performed.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@skabashnyuk @mkuznyetsov