The glance auth middleware also references X_USER & X_ROLE which were deprecated similarly to X_TENANT in favor of X_USER_ID, X_USER_NAME, and X_ROLES.
On Fri, Mar 9, 2012 at 9:53 AM, Kevin L. Mitchell < [email protected]> wrote: > On Fri, 2012-03-09 at 00:40 -0500, Jay Pipes wrote: > > So... the solution, I think, is to patch the glance_auth_token > > middleware in Keystone to use the value of the X_TENANT_ID header, not > > X_TENANT, and write some sort of data migration script to address the > > problem of stored owner_id values being name and not ID of tenant. > > Yeah, it's the problem of migration that caused me to use the tenant > name as opposed to the tenant ID, with the knowledge that we needed to > address this in the future. (The change that caused use of the tenant > name was due to a bug reported on glance having to do with the lack of > migration.) > -- > Kevin L. Mitchell <[email protected]> > > > _______________________________________________ > Mailing list: https://launchpad.net/~openstack > Post to : [email protected] > Unsubscribe : https://launchpad.net/~openstack > More help : https://help.launchpad.net/ListHelp >
_______________________________________________ Mailing list: https://launchpad.net/~openstack Post to : [email protected] Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
