Open Stack

On Tue, 2012-09-11 at 12:20 -0400, Adam Young wrote:
> I think that we can get away with the current set up for auth_token 
> middleware  (shipping it inside Keystone but deploying it as a stand 
> alone file) if we move its dependencies to openstack common.  Those 
> dependencies are:

Thinking about this some more ...

The auth_token middleware is a client for part of keystone's API.

It could be part of keystoneclient, or another library.

If it moves to openstack-commmon, it would eventually end up being
published as e.g. oslo-auth after going through an API stabilization
period (aka "incubation")

Do we gain anything from going this route? Could we not just publish a
keystone-authclient library containing the middleware?

Cheers,
Mark.