The environment variables that auth_token sets are documented in the module's docstring: https://github.com/openstack/keystone/blob/master/keystone/middleware/auth_token.py
As these variables are the defined interface for any projects consuming authentication services from middleware, it's safe to say they'll be supported be supported by any variations of auth_token, and will either continue to be supported or carefully deprecated. Speaking of, there are currently three headers that were deprecated prior to the release of essex (i.e. they were documented as deprecated in both essex and folsom), and could be reviewed for removal in grizzly (HTTP_X_USER, HTTP_X_ROLE, HTTP_X_TENANT). -Dolph On Mon, Oct 1, 2012 at 2:56 PM, Tong Li <liton...@us.ibm.com> wrote: > After a user gets authenticated, each following request will have a header > named HTTP_X_SERVICE_CATALOG which contains service end point links, can > any one tell me if it is safe to use the information contained in the > header to get the various end points from a filter in the pipeline? Notice > this header is set in the keystone, any other implementation of keystone > may choose not to include the information in the header, can anyone tell me > putting the endpoints in the headers is required by any implementation like > keystone for authentication? > > Thanks. > > Tong Li > Emerging Technologies & Standards > Building 501/B205 > liton...@us.ibm.com > > _______________________________________________ > Mailing list: https://launchpad.net/~openstack > Post to : openstack@lists.launchpad.net > Unsubscribe : https://launchpad.net/~openstack > More help : https://help.launchpad.net/ListHelp > >
_______________________________________________ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
