Repository navigation
Replies: 2 comments 8 replies
|
Check out the roles on the If you want all users to have these rights, add the roles to |
|
Afaik, you can not use the roles of the account client on the Admin API. This makes sense because you might want to restrict access to the Admin API in a different way as "self-service" functionality like the Account API. You can find some information on the "Account API" in this discussion. It should allow to change user data with account client roles. |
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
We use KeyCloak 21.0.1 and would like to allow certain user actions in our application that affect KeyCloak: e.g., allow users to request a Reset password link or to de-activate their account via our application. So a user does these actions in our application, which then calls upon the KeyCloak API to process them.
We have it working in the case the user is a realm-admin. But a "regular" user does not seem to have the rights (gets a Permission denied error from KeyCloak).
What user role do we need to give users to allow them to the accounts associated to managing their account?
It works when we give users the role of
[real-management] manage-usersbut then users can also do the actions for other user accounts, besides their own account. This is obviously not desirable.What is the appropriate user role for this use case?
All reactions