No key for your algorithm in the registered JWKS

What it means

The server read your registered JWKS but found no key for the algorithm you sign with (for example you sign RS384 but registered an EC key). You are probably signing with a different key than the one registered.

Fix

Sign with the private key whose public half is registered, or register this key (--show-public-jwk prints it).

Seen on real servers

server responseSMART launcher (launch.smarthealthit.org)

{
  "error": "invalid_client",
  "error_description": "None of the keys found in the JWKS have alg equal to RS384"
}

Check it with smart-doctor

Run your login and smart-doctor ranks this cause against the others, with the evidence it found.

npx smart-doctor check my-profile

Already have the server’s error? Explain it without running anything.

npx smart-doctor explain '{"error":"invalid_client","error_description":"None of the keys found in the JWKS have alg equal to RS384"}'