We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support issue https://jira.camunda.com/browse/SUPPORT-24829 https://jira.camunda.com/browse/SUPPORT-25323
Describe the Bug
The alg key is optional in the JWK Specification. Currently, we expect this key to be there or it throws an NPE.
alg
This works with Keycloak as the alg key is present, but with Entra for instance it might not work.
The fix should be backported to 8.6.
Steps to Reproduce
Expected Behavior
A 200 response should be returned as usual.
The text was updated successfully, but these errors were encountered:
More information was requested in the incident slack channel: https://camunda.slack.com/archives/C083JMZGUS2/p1734344977153109
Sorry, something went wrong.
The Connector should use the alg value which is part of the JWT headers as a fallback:
{ "typ": "JWT", "alg": "RS256", "x5t": "...", "kid": "..." }
mathias-vandaele
Successfully merging a pull request may close this issue.
Support issue
https://jira.camunda.com/browse/SUPPORT-24829
https://jira.camunda.com/browse/SUPPORT-25323
Describe the Bug
The
alg
key is optional in the JWK Specification. Currently, we expect this key to be there or it throws an NPE.This works with Keycloak as the
alg
key is present, but with Entra for instance it might not work.The fix should be backported to 8.6.
Steps to Reproduce
Expected Behavior
A 200 response should be returned as usual.
The text was updated successfully, but these errors were encountered: