Re: [openstack-dev] Kilo v3 identity problems

2015-06-03 Thread Steve Martinelli
Dolph Mathews dolph.math...@gmail.com wrote on 06/03/2015 02:16:55 PM: From: Dolph Mathews dolph.math...@gmail.com To: OpenStack Development Mailing List (not for usage questions) openstack-dev@lists.openstack.org Date: 06/03/2015 02:17 PM Subject: Re: [openstack-dev] Kilo v3 identity

[openstack-dev] Kilo v3 identity problems

2015-06-03 Thread Amy Zhang
Hi guys, I have installed Kilo and try to use identity v3. I am using v3 policy file. I changed the domain_id for cloud admin as default. As cloud admin, I tried openstack domain list and got the error message saying that I was not authorized. The part I changed in policy.json: cloud_admin:

Re: [openstack-dev] Kilo v3 identity problems

2015-06-03 Thread Rich Megginson
On 06/03/2015 10:29 AM, Amy Zhang wrote: Hi guys, I have installed Kilo and try to use identity v3. I am using v3 policy file. I changed the domain_id for cloud admin as default. As cloud admin, I tried openstack domain list and got the error message saying that I was not authorized. The

Re: [openstack-dev] Kilo v3 identity problems

2015-06-03 Thread Dolph Mathews
I assume that by v3 policy file you're specifically referring to: https://github.com/openstack/keystone/blob/f6c01dd1673b290578e9fff063e27104412ffeda/etc/policy.v3cloudsample.json Which essentially illustrates enforcement of a much more powerful authorization model than most deployers are

Re: [openstack-dev] Kilo v3 identity problems

2015-06-03 Thread Lin Hua Cheng
The command requires a domain scoped token. Did you set the environment variable so that OSC uses a domain scoped token? This can be done by providing OS_DOMAIN_NAME instead of OS_PROJECT_NAME. -Lin On Wed, Jun 3, 2015 at 9:29 AM, Amy Zhang amy.u.zh...@gmail.com wrote: Hi guys, I have