Skip to content

Client id_token_signed_response_alg metadata takes precedence over server get_jwt_config#843

Closed
azmeuk wants to merge 1 commit intoauthlib:mainfrom
azmeuk:806-id-token-alg
Closed

Client id_token_signed_response_alg metadata takes precedence over server get_jwt_config#843
azmeuk wants to merge 1 commit intoauthlib:mainfrom
azmeuk:806-id-token-alg

Conversation

@azmeuk
Copy link
Member

@azmeuk azmeuk commented Dec 11, 2025

What kind of change does this PR introduce?

When signing id_tokens, the client id_token_signed_response_alg metadata is used in priority.
Fixes #806.

Does this PR introduce a breaking change?

Before this, the value defined in get_jwt_config was used in priority, and id_token_signed_response_alg was only used if get_jwt_config does not provide alg.

This should only be merged for 1.7

  • You consent that the copyright of your pull request source code belongs to Authlib's author.

@azmeuk azmeuk added this to the Version 1.7 milestone Dec 11, 2025
@azmeuk azmeuk added the spec:oidc-core OpenID Connect Core 1.0 label Dec 11, 2025
@azmeuk
Copy link
Member Author

azmeuk commented Dec 11, 2025

Actually I will do it in a way that does not bring a breaking change.

@azmeuk azmeuk closed this Dec 11, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

spec:oidc-core OpenID Connect Core 1.0

Projects

None yet

Development

Successfully merging this pull request may close these issues.

id_token_signed_response_alg should take precedence to sign id_token

1 participant