-
Notifications
You must be signed in to change notification settings - Fork 4
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
Fine-grained authorisation for user account attributes #143
Comments
Manage account do extra things like giving access to being able to link Identity Provider. We can not simply replace this role. |
Updating multivalue attributes must be taken into account |
Another person have opened a github discussion for not being able to disable email change. Moreover, a question in Keycloak forum exists without sufficient response. They propose to make 'email as username' equals to true and disable changing username. However, I believe that this will also blocks Idp email change and we want to set 'email as username' to false together with 'Duplicate email's in order to support some email to different users. |
We could also use User profile, which is Technology preview that give us the ability to disable user from editing email from account console. Need to be tested. |
Unfortunately, we can not configure permissions in main attributes (fe email) like in other attributes. |
Currently Keycloak supports the
manage-account
role to control whether the user can update their name and email information (self-service). We want to introduce additional roles to limit access to name and email separately, e.g.manage-account-name
andmanage-account-email
.This is useful if for a given Keycloak installation we don't want users to change the name released by their Identity Provider but at the same time allow them to change their email which be trusted following the email verification process.
The text was updated successfully, but these errors were encountered: