Defines a Key Provider that can consume RS256 public keys published through an RFC-7517-compliant JWKS endpoint.
The resulting key can be used as a public key with the JWT module to validate a signed JWT. It can also be used with any other module that supports PEM-encoded RSA keys.
The provider is configured like any other part of a Key:

Known limitations
You can leave the "Key ID (kid)" field blank unless the JWKS endpoint is expected to return multiple keys. If the kid being returned isn't deterministic (e.g. it's auto-generated), you may have difficulty ensuring the desired key is used. We have not yet encountered this use case; if you do, please consider submitting a patch to provide a way to handle it.
Supporting organizations:
Main developers
| Attachment | Size |
|---|---|
| A sample configuration of the JWKS Key Provider. | 333.56 KB |
Project information
Seeking new maintainer
The current maintainers are looking for new people to take ownership.No further development
No longer developed by its maintainers.- Project categories: Security
- Ecosystem: JSON Web Token Authentication (JWT), Key
- Created by guypaddock on , updated
Stable releases for this project are covered by the security advisory policy.
There are currently no supported stable releases.
