Repository navigation
Client ID, Client Host, and Client IP Address protocol mappers #13602
Unanswered
jesseschmieg
asked this question in
Q&A
Replies: 3 comments
|
Hi, we are also stumbled over this. Can someone clarify why these mappers are created and are we safe to delete them? Up to now, we are not sure where and what exactly is the result of those mappers? Some insights would be nice. Thanks. |
0 replies
|
Same here |
0 replies
|
Client Id mapper,adding client_id claim, is based on OAuth2 specifications about client_id claim: If I am not wrong, this claim is related also to findind client user in token introspection and user info endpoint. |
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.
By default, a client with service accounts enabled automatically has created protocol mappers to map token claims for
clientId,clientHostandclientAddress. Even after deleting, there is logic to recreate these mappers upon token request if the Client ID mapper is not present. I'm curious about 1) if these claims serve some purpose beyond consumers of the tokens (for example, logging information when the tokens are used with Keycloak APIs) and 2) is there any way to avoid creating these mappers by default?Thank you - any help is appreciated.
All reactions