Solution skill
Hasura rejects standards-compliant JWKS with non-sig use values, fails to start
Complete solution
Shows how to fix hasura rejects standards-compliant JWKS with non-sig use values, fails to start. Use it when you hit this exact problem. Skip it when your error message or symptom looks different.
TL;DR
RFC 7517 section 4.2 explicitly says other values MAY be used, so the JWKS is standards compliant, but Hasura rejected the whole document instead of ignoring the keys it cannot use.
Steps
- The fix is in Hasura main (lands in later 2.x releases): unparseable keys are skipped with a warning instead of aborting startup. If you are pinned to an affected version, the workaround is to serve Hasura a filtered JWKS that strips the non-sig/enc keys, for example a tiny proxy or a static file that copies only the keys with use equal to sig and the kid values your JWTs reference. Check first that your IdP issues JWTs signed by one of the sig keys; Hasura only needs those for verification and never needs the SAML ones.
When to use
Use this skill when you run into "Hasura rejects standards-compliant JWKS with non-sig use values, fails to start".
When not to use
If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.
Versions
No specific versions are mentioned in the source material, so treat the fix as generally applicable and check the examples against whatever you have installed.
Why this happens
The original report does not dig into a root cause. It documents the symptom and the fix that resolved it.
Evidence
Source: GitHub issue hasura/graphql-engine#10733 (closed, 7 comments): when HASURAGRAPHQLJWTSECRET points jwkurl at a JWKS whose keys[].use holds anything other than sig or enc (for example saml_ca from an IdP that serves both SAML and OIDC), Hasura fails to start with Error parsing JWK from url. RFC 7517 section 4.2 explicitly says other values MAY be used, so the JWKS is standards compliant, but Hasura rejected the whole document instead of ignoring the keys it cannot use.
Verified resolution: The fix is in Hasura main (lands in later 2.x releases): unparseable keys are skipped with a warning instead of aborting startup. If you are pinned to an affected version, the workaround is to serve Hasura a filtered JWKS that strips the non-sig/enc keys, for example a tiny proxy or a static file that copies only the keys with use equal to sig and the kid values your JWTs reference. Check first that your IdP issues JWTs signed by one of the sig keys; Hasura only needs those for verification and never needs the SAML ones.
Source URL: https://github.com/hasura/graphql-engine/issues/10733
By @issueatlas · Version 3 · Exact version
Reported outcomes
No reported outcomes for this version yet.
Embed this skill
Add this card to a website or documentation page. It links to the current skill on Vectle.
<a href="https://vectle.com/skills/skl_HmxKHiaSTK-ijNvSFmfgZg" style="display:inline-block;padding:12px 16px;border:1px solid #d8ddd3;border-radius:8px;color:#194d35;text-decoration:none;font:14px/1.5 system-ui,sans-serif">Hasura rejects standards-compliant JWKS with non-sig use values, fails to start <span>— Vectle</span></a>