]
Sent: Wednesday, November 14, 2012 2:47 PM
To: OpenStack Development Mailing List
Cc: openstack@lists.launchpad.net (openstack@lists.launchpad.net)
Subject: Re: [openstack-dev] [Openstack] Fwd: [keystone] Tokens
representing
authorization to projects/tenants in the Keystone V3 API
From
(openstack@lists.launchpad.net)
Subject: Re: [openstack-dev] [Openstack] Fwd: [keystone] Tokens representing
authorization to projects/tenants in the Keystone V3 API
From an API perspective the changes required are the following:
1. The validate call returns a list of tenants instead
: openstack@lists.launchpad.net (openstack@lists.launchpad.net)
Subject: Re: [openstack-dev] [Openstack] Fwd: [keystone] Tokens
representing
authorization to projects/tenants in the Keystone V3 API
From an API perspective the changes required are the following:
1. The validate call
@lists.launchpad.net)
Subject: Re: [openstack-dev] [Openstack] Fwd: [keystone] Tokens representing
authorization to projects/tenants in the Keystone V3 API
From an API perspective the changes required are the following:
1. The validate call returns a list of tenants instead of a single
tenant
Mailing List
Cc: openstack@lists.launchpad.net (openstack@lists.launchpad.net)
Subject: Re: [Openstack] [openstack-dev] Fwd: [keystone] Tokens representing
authorization to projects/tenants in the Keystone V3 API
On Nov 13, 2012, at 11:01 AM, Jorge Williams jorge.willi...@rackspace.com
wrote
@lists.launchpad.net
(openstack@lists.launchpad.net)
Subject: Re: [Openstack] [openstack-dev] Fwd: [keystone] Tokens representing
authorization to projects/tenants in the Keystone V3 API
Hey Joe:
Currently a user scoped token doesn't include a service catalog - mostly
because I think the service
Cc: openstack@lists.launchpad.net (openstack@lists.launchpad.net)
Subject: Re: [Openstack] [openstack-dev] Fwd: [keystone] Tokens
representing authorization to projects/tenants in the Keystone V3 API
On Nov 13, 2012, at 11:01 AM, Jorge Williams jorge.willi...@rackspace.com
wrote:
On Nov
@lists.launchpad.net (openstack@lists.launchpad.net)
Subject: Re: [openstack-dev] [Openstack] Fwd: [keystone] Tokens representing
authorization to projects/tenants in the Keystone V3 API
From an API perspective the changes required are the following:
1. The validate call returns a list
On 11/10/2012 10:58 AM, David Chadwick wrote:
I agree with the vast majority of what Jorge says below. The idea I
would like to bounce around is that of the unscoped token.
What does it mean conceptually? What is its purpose? Why do we need
it? Why should a user be given an unscoped token to
Hi Adam
you have pointed out an important difference between an unscoped token
and a scoped one. The former can only be used with keystone, the latter
with a cloud service. This also implies that a scoped token can only
have the scope of a single service, and not multiple services. The user
+guang.yee=hp@lists.launchpad.net] On Behalf Of
David Chadwick
Sent: Tuesday, November 13, 2012 7:32 AM
To: Adam Young
Cc: OpenStack Development Mailing List; openstack@lists.launchpad.net
Subject: Re: [Openstack] [openstack-dev] Fwd: [keystone] Tokens representing
authorization to projects/tenants
: Tuesday, November 13, 2012 7:32 AM
To: Adam Young
Cc: OpenStack Development Mailing List; openstack@lists.launchpad.net
Subject: Re: [Openstack] [openstack-dev] Fwd: [keystone] Tokens representing
authorization to projects/tenants in the Keystone V3 API
Hi Adam
you have pointed out an important
Chadwick
Sent: Tuesday, November 13, 2012 7:32 AM
To: Adam Young
Cc: OpenStack Development Mailing List; openstack@lists.launchpad.net
Subject: Re: [Openstack] [openstack-dev] Fwd: [keystone] Tokens representing
authorization to projects/tenants in the Keystone V3 API
Hi Adam
you have pointed
[mailto:openstack-bounces+guang.yee=hp@lists.launchpad.net]
On Behalf Of David Chadwick Sent: Tuesday, November 13, 2012 7:32
AM To: Adam Young Cc: OpenStack Development Mailing List;
openstack@lists.launchpad.net Subject: Re: [Openstack]
[openstack-dev] Fwd: [keystone] Tokens representing
, 2012 7:32 AM
To: Adam Young
Cc: OpenStack Development Mailing List; openstack@lists.launchpad.net
Subject: Re: [Openstack] [openstack-dev] Fwd: [keystone] Tokens representing
authorization to projects/tenants in the Keystone V3 API
Hi Adam
you have pointed out an important difference between
: Tuesday, November 13, 2012 7:32 AM
To: Adam Young
Cc: OpenStack Development Mailing List; openstack@lists.launchpad.net
Subject: Re: [Openstack] [openstack-dev] Fwd: [keystone] Tokens
representing
authorization to projects/tenants in the Keystone V3 API
Hi Adam
you have pointed out
On Nov 13, 2012, at 11:01 AM, Jorge Williams jorge.willi...@rackspace.com
wrote:
On Nov 13, 2012, at 11:35 AM, heckj wrote:
So maintaining a token scoped to just the user, and a mechanism to scope it
to a tenant sound like all goodness. We can absolutely keep the API such
that it can
@lists.launchpad.net)
Subject: Re: [Openstack] [openstack-dev] Fwd: [keystone] Tokens representing
authorization to projects/tenants in the Keystone V3 API
On Nov 13, 2012, at 11:01 AM, Jorge Williams jorge.willi...@rackspace.com
wrote:
On Nov 13, 2012, at 11:35 AM, heckj wrote:
So maintaining a token
: [Openstack] [openstack-dev] Fwd: [keystone] Tokens representing
authorization to projects/tenants in the Keystone V3 API
On Nov 13, 2012, at 11:01 AM, Jorge Williams jorge.willi...@rackspace.com
wrote:
On Nov 13, 2012, at 11:35 AM, heckj wrote:
So maintaining a token scoped to just the user
I agree with the vast majority of what Jorge says below. The idea I
would like to bounce around is that of the unscoped token.
What does it mean conceptually? What is its purpose? Why do we need it?
Why should a user be given an unscoped token to exchange at a later time
for a scoped token?
20 matches
Mail list logo
