Repository navigation
Replies: 1 comment
|
The feature also raise the problem of identifying a role. There is already the syntax realm-role , client-id.client-role. But we will probably need a syntax for the organization-role with the problem that client-id and organization-id or organization-alias might overlap with client-id. An idea might be to us *org:org-alias.org-role (and may start accepting [client:]client-id.client-role and [realm:]realm-role with the client: and realm: prefix being optional and not included when keycloak expose the string. |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
I fork a discussion here #45238 - Support attaching roles to user invitations.
It raise a question about the proper error handling. If we support a reference to a role (or a group btw) in the invitation, this reference should probably be validated.
We can certainly check that the role exists when the invitation is created.
But what should be the behavior is the role (group) doesn't exists anymore when the user actually register ?
All reactions