Skip to content

get_jwt_config takes a client parameter.#844

Merged
lepture merged 1 commit intoauthlib:mainfrom
azmeuk:806-get-jwt-config-client
Dec 12, 2025
Merged

get_jwt_config takes a client parameter.#844
lepture merged 1 commit intoauthlib:mainfrom
azmeuk:806-get-jwt-config-client

Conversation

@azmeuk
Copy link
Member

@azmeuk azmeuk commented Dec 11, 2025

What kind of change does this PR introduce?

Add a client parameter to get_jwt_config so people can use client.id_token_signed_response_alg in get_jwt_config.

Supersedes #843
Related to #806. It does not fix it because client.id_token_signed_response_alg should be the default, but at least it allows for a smooth transition.

Checklist

  • The commits follow the conventional commits specification.
  • You ran the linters with prek.
  • You wrote unit test to demonstrate the bug you are fixing, or to stress the feature you are bringing.
  • You reached 100% of code coverage on the code you edited, without abusive use of pragma: no cover
  • If this PR is about a new feature, or a behavior change, you have updated the documentation accordingly.

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

@azmeuk azmeuk requested a review from lepture December 11, 2025 14:37
@azmeuk azmeuk added the spec:oidc-core OpenID Connect Core 1.0 label Dec 11, 2025
This allows to use the client.id_token_signed_response_alg metadata in
get_jwt_config
@azmeuk azmeuk force-pushed the 806-get-jwt-config-client branch from c7e7726 to 714502a Compare December 11, 2025 14:38
@lepture lepture merged commit 0a423d4 into authlib:main Dec 12, 2025
8 checks passed
@azmeuk azmeuk deleted the 806-get-jwt-config-client branch December 12, 2025 08:00
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.

2 participants