OAuth Token Validation Caching

This little addition on top of cloudbees-api-client provides an OAuth token validator with the decoration pattern of adding in-memory client-side caching.

This reduces the number of calls to the OAuth server (aka Grand Central), and allows the client to continue service even in the case of the OAuth server outage.

Usage

// if you are validating tokens, you are most likely OAuth client yourself.
BeesClient bees = new BeesClient(clientId,clientSecret);

// this creates non-cached plain-vanilla validator
TokenValidator v = TokenValidator.from(bees);

// decorates v with caching
v = v.withCache();

...

OauthToken t = v.validateToken(tokenThatCameFromHttpRequest)
if (t==null)    throw new SecurityException("invalid token: "+tokenThatCameFromHttpRequest);

Mock Test

When you are testing your code that uses TokenValidator, it is often convenient to be able to run tests without talking to the actual OAuth server. For this purpose, this library provides MockTokenValidator in the tests jar.

To use this, add the following in your POM as a dependency:

<dependency>
  <groupId>com.cloudbees</groupId>
  <artifactId>token-validator</artifactId>
  <classifier>tests</classifier>
  <version>1.0</version>
  <scope>test</scope>
</dependency>

This class constructs OauthToken object just from the textual representation of the token it gets, such as "account=kohsuke,scope=...". See its javadoc for the details.