[openstack-dev] Moving auth_token middleware dependencies to openstack common

Dolph Mathews dolph.mathews at gmail.com
Tue Sep 11 19:08:18 UTC 2012

I think ideally auth_token would be re-written to depend on keystoneclient,
but I wouldn't intuitively look for WSGI middleware in a python client
library. I'd prefer either openstack-common or a whole new package.


On Tue, Sep 11, 2012 at 1:42 PM, Mark McLoughlin <markmc at redhat.com> wrote:

> 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.
> _______________________________________________
> OpenStack-dev mailing list
> OpenStack-dev at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20120911/1eea95e5/attachment.html>

More information about the OpenStack-dev mailing list