OWIN setup similar to Google Service Accounts using JWT Bearer tokens

I've got a WebAPI 2 service that I would like to have a security setup very similar to the Google Service Accounts. The consuming application would send a JWT to the token endpoint to get an access token which would then be sent on all subsequent calls to the service until that token expires. 
Additional requirements:
The preference would be that token endpoint would be part of the service application and not a separately hosted application. Because is going to be load balanced and I can't rely on sticky sessions I would need to store the access tokens in a central place like a database. I'd like to be able to control the expiration time of the access token. Like Google Service Accounts each application authenticating will have a different client_id (Issuer) and a different signing key. How would one set this up using OWIN?
...