On Tue, May 6, 2014 at 3:17 AM, Roman Bodnarchuk <
roman.bodnarc...@indigitus.ch> wrote:
> Thanks for reply. I think I got the justifications for such an approach.
>
> BTW, is there a resource, which can be used to track support of Keystone
> v3 (and domain-based policies) among OS services? Are
Thanks for reply. I think I got the justifications for such an approach.
BTW, is there a resource, which can be used to track support of Keystone
v3 (and domain-based policies) among OS services? Are there some
defined plans for moving whole OS to v3 and domains?
--
Roman
On 4/28/2014 6:43
On Thu, 2014-04-17 at 19:58 +0300, Roman Bodnarchuk wrote:
> Hello,
>
> I am trying to make sure that a user can't do anything useful with an
> unscoped token, and got to the following code in
> keystoneclient.middleware.auth_token:
>
> if _token_is_v2(token_info) and not auth_ref.proj
Hello,
I am trying to make sure that a user can't do anything useful with an
unscoped token, and got to the following code in
keystoneclient.middleware.auth_token:
if _token_is_v2(token_info) and not auth_ref.project_id:
raise InvalidUserToken('Unable to determine tenancy.
