Skip to content
This repository has been archived by the owner on Feb 11, 2023. It is now read-only.

JWT Signing keys are not found when application has custom signing keys in Azure AD #85

Open
tuomovee opened this issue Mar 2, 2021 · 0 comments

Comments

@tuomovee
Copy link

tuomovee commented Mar 2, 2021

JWT signature validation fails to discover signing keys when the application has custom signing keys - for example due to usage of the claims-mapping feature.

This can be resolved by appending query parameter "appid" with value matching client/application id to the discovery URL.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant