8000
|
Your approach makes sense. Extending Keycloak just to add a hardcoded claim is simply overkill. |
|
Thank you for the idea of using an already existing scope! In regards to extending Keycloak, the only reason I am thinking about it, is because this is crucial information that should have a single source of truth and also reducing the possibility of a wrongly configured client. If I was to try and solve this by extending Keycloak, where should I be looking at? |
Uh oh!
There was an error while loading. Please reload this page.
Hello,
I am working with Keycloak 21.1.2, and am in need to provide clients with a
realmTypeclaim. This claim value has to be same for every client of the realm. From the information that I had gathered so far, the way to do this is to define a new client scope and set its Type to Default, then register a mapper on it that will provide therealmTypehard-coded claim. This scope will then be added to any newly created client, but has to be added manually to any clients that existed prior scope creation.Is this the correct way of providing the same claim value to all clients or am I taking the wrong approach? Should I be doing something else by extending/implementing some keycloak SPI class?
All reactions