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

Open
ssilvert wants to merge 1 commit into
keycloak:mainfrom
ssilvert:issue-50505-upgrade-note
Open

ssilvert wants to merge 1 commit into
keycloak:mainfrom
ssilvert:issue-50505-upgrade-note

Conversation

@ssilvert
Copy link
Copy Markdown
Contributor

Adds an upgrade guide entry for the fix in #54401. Starting with 27.0.0, default values of user profile attributes are stored for new users who cannot edit the attribute.

The entry goes under Notable changes in changes-27_0_0.adoc. It explains that:

  • tokens can now include claims for these attributes that were previously missing;
  • users created before the upgrade are not backfilled;
  • administrators can store the value by saving the user in the Admin Console or by updating the attribute through the Admin REST API.

Fixes #50505

Assisted-by: Claude Opus 5.5

Copilot AI balanced review requested due to automatic review settings October 29, 2026 18:12
@ssilvert
ssilvert requested a review from a team as a code owner October 29, 2026 18:12
Copilot AI left a comment
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🟢 Approval recommended

No active review issues remain for the documentation-only upgrade note explaining user-profile default persistence and manual updates for existing users.

No open issues 🎉

What changed in this PR

Adds a Keycloak 27.0.0 upgrade note documenting the user profile fix in #54401 for issue #50505. This PR changes documentation only.

Changes:

  • Explains that configured defaults are now stored for newly created users who cannot edit the attribute, allowing previously missing token claims to appear.
  • Clarifies that existing users are not updated automatically and describes how administrators can store their values.
File Description
docs/​documentation/​upgrading/​topics/​changes/​changes-27_0_0.adoc Adds a notable-change entry covering default-value persistence, token impact, and manual updates for existing users.

Review effort: Balanced

@ssilvert
ssilvert force-pushed the issue-50505-upgrade-note branch from ff9a942 to f5e4fbb Compare November 6, 2026 14:06
Copilot AI balanced review requested due to automatic review settings November 6, 2026 14:06
Copilot AI left a comment
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🟢 Approval recommended

No active review issues remain for the upgrade note covering default-value persistence and remediation for existing users.

No open issues 🎉

Review effort: Balanced

Users created before the upgrade are not backfilled, so administrators
need to know that their existing users may still lack the stored value
and how to fix it.

Fixes keycloak#50505

Signed-off-by: Stan Silvert <ssilvert@redhat.com>
Assisted-by: Claude Opus 5.5
@ssilvert
ssilvert force-pushed the issue-50505-upgrade-note branch from f5e4fbb to 337a56a Compare November 6, 2026 18:30
Copilot AI balanced review requested due to automatic review settings November 6, 2026 18:30
Copilot AI left a comment
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🟢 Approval recommended

No active review issues were identified for the upgrade guidance on default-value persistence and existing-user updates.

No open issues 🎉

Review effort: Balanced

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

User Profile attribute default value not persisted on user creation, missing in jwt user attribute

2 participants

0