Repository navigation
User attribute that can be accessed by user, but not exposed in the update profile form #36141
Replies: 1 comment
|
I found the perfect solution to this. Since I'm also implementing a custom authenticator, I added a |
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.
Uh oh!
There was an error while loading. Please reload this page.
Currently, a managed attribute that has the
Who can view?set to true forUseris visible in the post-login update profile form. I would like to have an attribute invisible in this form, but can otherwise be retrieved on browser client side throughkeycloak.loadUserProfileor something else. This is to support customizing UI based on user metadata. It does not even need to be a custom attribute, if there's some other machanism for passing user metadata to frontend. Probably not put into the JWT token though. Is that possible? Is my only option to customize the template for the update profile form?All reactions