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.

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

Revise functionality of Profile & Security page #5788

Closed
skabashnyuk opened this issue Jul 24, 2017 · 4 comments
Closed

Revise functionality of Profile & Security page #5788

skabashnyuk opened this issue Jul 24, 2017 · 4 comments
Assignees
Labels
kind/task Internal things, technical debt, and to-do tasks to be performed.

Comments

@skabashnyuk
Copy link
Contributor

Now, these pages look like this.

2017-07-24 11 41 20
2017-07-24 11 41 14

The functionality of this pages is supported by ProfileService. But in the case of integration of keycloak all this information are not stored in Che database and delighted to ID provide service (keycloak in our case). In this #5438 we are going provide an ability to get some information for ProfileService from Keycloak via OpenID protocol. In the first stage, it will be this fields

{
  "sub": "c8785721-f72d-4628-a9b5-391ff65f7b93",
  "name": "max shaposhnik",
  "preferred_username": "uy7c",
  "given_name": "max",
  "family_name": "shaposhnik",
  "email": "uy7c2@yahoo.com"
}

A couple of notes to consider.

  1. ProfileService will be readonly.
  2. Consider to redirect to profile and change passwor page insted of editing it directly.
@skabashnyuk skabashnyuk added kind/task Internal things, technical debt, and to-do tasks to be performed. team/plugin labels Jul 24, 2017
@skabashnyuk skabashnyuk mentioned this issue Jul 24, 2017
25 tasks
@ashumilova ashumilova self-assigned this Jul 24, 2017
@mshaposhnik
Copy link
Contributor

mshaposhnik commented Sep 4, 2017

Profile endpoint URL will be available at /api/keycloak/settings under the che.keycloak.profile.endpoint and che.keycloak.password.endpoint key.

@skabashnyuk
Copy link
Contributor Author

This is how
/api/keycloak/settings looks like
2017-09-05 11 51 34
profile page
2017-09-05 12 02 45
Password
2017-09-05 12 02 47
Logout url looks like

http://192.168.65.2:5050/auth/realms/che/protocol/openid-connect/logout?redirect_uri=http%3A%2F%2F192.168.65.2%3A5050%2Fauth%2Frealms%2Fche%2Faccount%2F
See more http://www.keycloak.org/docs/3.2/securing_apps/topics/oidc/java/logout.html

@ashumilova @slemeur please revise this info. Do you need something else?

@slemeur
Copy link
Contributor

slemeur commented Sep 5, 2017

Curious, why do you think we need to redirect to keycloack pages? Are we not able to reuse the pages that we already have and connect them to the keycloak API?

@skabashnyuk
Copy link
Contributor Author

I doubt that such API exists.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/task Internal things, technical debt, and to-do tasks to be performed.
Projects
None yet
Development

No branches or pull requests

4 participants