# AZ719: A key set with no key to check tokens with

`authz.set_jwks` stores the keys an identity provider signs its tokens with, as the provider serves them (a JWKS), and the set it is given replaces the stored one. This set holds no key `authz.login_jwt` checks an RS256 token with: an RSA key (`kty`) for signatures (`use` absent or `sig`, `key_ops` absent or with `verify`, `alg` absent or `RS256`) of 2048 to 4096 bits with the exponent 65537. The error's detail says why each key was skipped, or that the set holds none. The usual causes: the answer of a fetch that failed (an error page, an empty body), a provider that signs with another algorithm (ES256, EdDSA: check those tokens in the backend and sign in with `authz.act_as`), or keys under 2048 bits. Nothing changed: the stored keys stay, so a fetch that failed signs nobody out. The call is the owner's (an administrator's, a job's that runs when the keys change), not a request's: the SDKs give this error no answer of its own, and a request that met it would be left an error, a 500. SQLSTATE 22023.

Reported to the app, by the `authz.*` functions and the policy's rules: the code is in the error's HINT (`rowstile help AZ719`), and the SDKs' errors carry it as `code`.
