jwks-rsa
Install
Maven
<dependency>
<groupId>com.auth0</groupId>
<artifactId>jwks-rsa</artifactId>
<version>0.17.0</version>
</dependency>
Gradle
implementation 'com.auth0:jwks-rsa:0.17.0'
Usage
The JSON Web Tokens you get from the Authorization Server include a key id header parameter ("kid"), used to uniquely identify the Key used to sign the token.
i.e.: Given the following JWT:
eyJ0eXAiOiJKV1QiLCJhbGciOiJSUzI1NiIsImtpZCI6IlJrSTVNakk1T1VZNU9EYzFOMFE0UXpNME9VWXpOa1ZHTVRKRE9VRXpRa0ZDT1RVM05qRTJSZyJ9.eyJpc3MiOiJodHRwczovL3NhbmRyaW5vLmF1dGgwLmNvbS8iLCJzdWIiOiJhdXRoMHw1NjMyNTAxZjQ2OGYwZjE3NTZmNGNhYjAiLCJhdWQiOiJQN2JhQnRTc3JmQlhPY3A5bHlsMUZEZVh0ZmFKUzRyViIsImV4cCI6MTQ2ODk2NDkyNiwiaWF0IjoxNDY4OTI4OTI2fQ.NaNeRSDCNu522u4hcVhV65plQOiGPStgSzVW4vR0liZYQBlZ_3OKqCmHXsu28NwVHW7_KfVgOz4m3BK6eMDZk50dAKf9LQzHhiG8acZLzm5bNMU3iobSAJdRhweRht544ZJkzJ-scS1fyI4gaPS5aD3SaLRYWR0Xsb6N1HU86trnbn-XSYSspNqzIUeJjduEpPwC53V8E2r1WZXbqEHwM9_BGEeNTQ8X9NqCUvbQtnylgYR3mfJRL14JsCWNFmmamgNNHAI0uAJo84mu_03I25eVuCK0VYStLPd0XFEyMVFpk48Bg9KNWLMZ7OUGTB_uv_1u19wKYtqeTbt9m1YcPMQ
Decode it using any JWT library or tool like jwt.io and extract the kid parameter from the Header claims.
{
"typ": "JWT",
"alg": "RS256",
"kid": "RkI5MjI5OUY5ODc1N0Q4QzM0OUYzNkVGMTJDOUEzQkFCOTU3NjE2Rg"
}
Use this kid on any of the JwkProviders enumerated below to obtain the signing key provided by the JWKS endpoint you've configured.
UrlJwkProvider
UrlJwkProvider fetches the jwk from /.well-known/jwks.json of the supplied domain issuer and returns a Jwk if the kid matches one of the registered keys.
JwkProvider provider = new UrlJwkProvider("https://samples.auth0.com/");
Jwk jwk = provider.get("{kid of the signing key}"); //throws Exception when not found or can't get one
Also it can load jwks.json file from any given Url (even to a local file in your filesystem).
JwkProvider provider = new UrlJwkProvider(new URL("https://samples.auth0.com/"));
Jwk jwk = provider.get("{kid of the signing key}"); //throws Exception when not found or can't get one
GuavaCachedJwkProvider
GuavaCachedJwkProvider cache the jwk in a LRU in memory cache, if the jwk is not found in the cache it will ask another provider for it and store it's result in the cache.
By default it stores 5 keys for 10 minutes, but these values can be changed.
JwkProvider http = new UrlJwkProvider("https://samples.auth0.com/");
JwkProvider provider = new GuavaCachedJwkProvider(http);
Jwk jwk = provider.get("{kid of the signing key}"); //throws Exception when not found or can't get one
RateLimitJwkProvider
RateLimitJwkProvider will limit the amounts of different signing keys to get in a given time frame.
By default the rate is limited to 10 different keys per minute but these values can be changed.
JwkProvider url = new UrlJwkProvider("https://samples.auth0.com/");
Bucket bucket = new Bucket(10, 1, TimeUnit.MINUTES);
JwkProvider provider = new RateLimitJwkProvider(url, bucket);
Jwk jwk = provider.get("{kid of the signing key}"); //throws Exception when not found or can't get one
JwkProviderBuilder
To create a provider for domain https://samples.auth0.com with cache and rate limit:
JwkProvider provider = new JwkProviderBuilder("https://samples.auth0.com/")
.build();
Jwk jwk = provider.get("{kid of the signing key}"); //throws Exception when not found or can't get one
and specifying cache and rate limit attributes:
JwkProvider provider = new JwkProviderBuilder("https://samples.auth0.com/")
.cached(10, 24, TimeUnit.HOURS)
.rateLimited(10, 1, TimeUnit.MINUTES)
.build();
Jwk jwk = provider.get("{kid of the signing key}"); //throws Exception when not found or can't get one
Error handling
There are certain scenarios in which this library can fail. Read below to understand what to expect and how to handle the errors.
Missing JSON Web Key
This error may arise when the hosted JSON Web Key set (JWKS) file doesn't represent a valid set of keys, or is empty. They are raised as a SigningKeyNotFoundException. The cause would need to be inspected in order to understand the specific failure reason.
Network error
There's a special case for Network errors. These errors represent timeouts, invalid URLs, or a faulty internet connection. They may occur when fetching the keys from the given URL. They are raised as a NetworkException instance.
If you need to detect this scenario, make sure to check it before the catch of SigningKeyNotFoundException.
try {
// ...
} catch (NetworkException e) {
// Network error
} catch (SigningKeyNotFoundException e) {
// Key is invalid or not found
}
Unsupported JSON Web Key
When the received key is not of a supported type, or the attribute values representing it are wrong, an InvalidPublicKeyException will be raised. The following key types are supported:
- RSA
- Elliptic Curve
- P-256
- P-384
- P-521
Rate limits
When using a rate-limited provider, a RateLimitReachedException error might be raised when the limit is breached. The instance can help determine how long to wait until the next call would be available.
try {
// ...
} catch (RateLimitReachedException e) {
long waitTime = e.getAvailableIn()
// wait until available
}
What is Auth0?
Auth0 helps you to:
- Add authentication with multiple authentication sources, either social like Google, Facebook, Microsoft Account, LinkedIn, GitHub, Twitter, Box, Salesforce, amont others, or enterprise identity systems like Windows Azure AD, Google Apps, Active Directory, ADFS or any SAML Identity Provider.
- Add authentication through more traditional username/password databases.
- Add support for linking different user accounts with the same user.
- Support for generating signed Json Web Tokens to call your APIs and flow the user identity securely.
- Analytics of how, when and where users are logging in.
- Pull data from other sources and add it to the user profile, through JavaScript rules.
Create a free Auth0 Account
- Go to Auth0 and click Sign Up.
- Use Google, GitHub or Microsoft Account to login.
Issue Reporting
If you have found a bug or if you have a feature request, please report them at this repository issues section. Please do not report security vulnerabilities on the public GitHub issue tracker. The Responsible Disclosure Program details the procedure for disclosing security issues.
Author
License
This project is licensed under the MIT license. See the LICENSE file for more info.
8.8k Dec 30, 2022
274 Dec 28, 2022
2 Dec 8, 2021
7 Jul 31, 2022
140 Dec 1, 2022
150 Dec 5, 2022
45 Nov 15, 2022
55 Jan 6, 2023
18 Jul 16, 2022
19 May 28, 2022
2 Oct 21, 2021
15 Oct 22, 2022
1 Jan 4, 2022
2 Nov 5, 2022
17 Nov 7, 2022
303 Dec 30, 2022
59 Sep 17, 2022
6 Jul 10, 2022
519 Dec 31, 2022
35 Jul 1, 2022