Cloned from launchpad blueprint https://blueprints.launchpad.net/keystone/+spec/use-keystoneclient.

Description:

Token checking/validating in keystone for authenticated functions is spread over a wide range of files, some which check admin, some which retrieve the token data some which actually authenticate and some which don't. 

This is ludicrous, we have auth token middleware that we provide to other applications, the authenticated sections of keystone should also rely on this mechanism. This would involve figuring out providing certificates to the middleware for pki tokens, properly understanding what requires authentication and at what level. This would hopefully also mean that we may not have a need to save the token metadata to the database, we could simply rely on the signed token passed to keystone in the way that other projects do and simply save token data for revocation purposes. 

Specification URL (additional information):

None