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 <henryna...@mac.com> wrote:
> 
> 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 for get_user to be 
> the same if you want to allow users to read their own user record.
> 
> Henry
> Sent from my iPad
> 
>> On 11 May 2016, at 09:49, Ehsan Qarekhani <qarekh...@gmail.com> wrote:
>> 
>> 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.
>> __________________________________________________________________________
>> OpenStack Development Mailing List (not for usage questions)
>> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
> 
> __________________________________________________________________________
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Reply via email to