8000 Document stored default values for read-only user profile attributes by ssilvert · Pull Request #54466 · keycloak/keycloak · GitHub
[go: up one dir, main page]
Skip to content

Document stored default values for read-only user profile attributes #54466

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
ssilvert wants to merge 1 commit into
base: main
Choose a base branch
from
+13 −0
Open

Document stored default values for read-only user profile attributes #54466

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
13 changes: 13 additions & 0 deletions docs/documentation/upgrading/topics/changes/changes-27_0_0.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -483,6 +483,19 @@ This change follows the secure-by-default policy.
To restore the previous behavior, click the *Send Reset Email* settings icon in the reset credentials flow, define an *Alias*, and set *Force login after reset* to `false` to keep the user logged in when the same browser is used, or to `only-federated` to force re-authentication only for federated users.
For more information, see link:{adminguide_link}#enabling-forgot-password[Enable forgot password].

=== Default values of user profile attributes are stored for new users who cannot edit the attribute
// https://github.com/keycloak/keycloak/issues/50505

Previously, when a user profile attribute had a default value but users could not edit the attribute, the default value was not stored for users created through self-registration or first broker login.
The Admin Console displayed the default value for these users, but protocol mappers, exports, and anything else reading stored user attributes found no value.

Starting with this release, the default value is stored when these users are created.
As a result, tokens can now include claims for these attributes that were previously missing.

Existing users are not updated automatically.
Users created before the upgrade have no stored value for these attributes unless an administrator has since saved the user.
To store the default value for such users, save each user in the Admin Console, or update the attribute through the Admin REST API.

// ------------------------ Deprecated features ------------------------ //
== Deprecated features

Expand Down
Loading
0