Skip to content

Support jwt guarded identity via custom token claim #1276

@jfallows

Description

@jfallows

Describe the desired outcome from the user's perspective
As an app developer, I need to configure my application's concept of user identifier with a stable value that is not dynamically generated.

Acceptance criteria

  • Support configuration of a custom jwt token claim to return as guarded identity value
  • Continue to use sub claim by default, for backwards compatibility

Additional context
Note that keycloak creates a dynamic internal identifier used as sub claim in jwt access token for authorized users, whereas preferred_username claim is required to be unique and is also stable.

Metadata

Metadata

Assignees

Labels

storyFeature description from user's perspective

Type

No type
No fields configured for issues without a type.

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions