Re: [openstack-dev] [keystone][api][v3]

2016-05-11 Thread Dean Troyer
On Wed, May 11, 2016 at 4:30 AM, Henry Nash wrote: > Oops "uncooked"! I meant unscoped! (thank you Apple's auto-correct spell > checker!) > Heh, I read right past that and knew what you meant... somehow I really like 'uncooked', we should keep it around a while... ;) dt --

Re: [openstack-dev] [keystone][api][v3]

2016-05-11 Thread Henry Nash
Oops "uncooked"! I meant unscoped! (thank you Apple's auto-correct spell checker!) Sent from my iPad > On 11 May 2016, at 10:25, Henry Nash wrote: > > Hi > > This depends on the policy rule for the get_user call - which is defined by > your policy.json file for your

Re: [openstack-dev] [keystone][api][v3]

2016-05-11 Thread Henry Nash
Hi This depends on the policy rule for the get_user call - which is defined by your policy.json file for your keystone. In the default one supplied you need admin to do this, unlike change password where the owner (I.e. A user with an uncooked token) can execute. You could change my the rule

[openstack-dev] [keystone][api][v3]

2016-05-11 Thread Ehsan Qarekhani
HI is there any way to retrieve default_project_id of login user from unscoped token ? as I know I able to retrieve all projects which user can access but I can't tell which one is user default project. Many thanks in advance.