You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Defining a config item id_token_signing_alg_values_supported is respected and reflected in the entity registration, but said registered entity is apparently not used when checking what signing algo should be supported.
Full example that fails against Kanidm when used via SaToSa as a backend:
For testing I changed the line to instead look for ES256. This allows validation to pass and auth works fine after this, even if I don't manually specify id_token_signing_alg_values_supported.
If the check is necessary, it should be expanded to other algos, or perhaps take the OP discovery id_token_signing_alg_values_supported and check for the algos given there.
Ooor, the smallest dumbest fix would be to check for either RS256 or ES256, I don't have the context for why this check was necessary in the first place. :-)
The verify code at:
https://github.com/IdentityPython/idpy-oidc/blob/main/src/idpyoidc/message/oidc/__init__.py#L945 hardcodes checking that the OP supports
RS256
for id_token_signing. There doesn't seem to be any config option that would allow overriding this and thus OPs that on purpose require better algorithms cannot be supported. In my case Kanidm requires ES256 be used, and signals so in discovery.Defining a config item
id_token_signing_alg_values_supported
is respected and reflected in the entity registration, but said registered entity is apparently not used when checking what signing algo should be supported.Full example that fails against Kanidm when used via SaToSa as a backend:
Failure via SaToSa load:
The text was updated successfully, but these errors were encountered: