- Original Message -
> From: "michael mccune"
> To: openstack-dev@lists.openstack.org
> Sent: Friday, August 7, 2015 1:21:53 AM
> Subject: Re: [openstack-dev] [keystone] policy issues when generating trusts
> with different clients
>
> On 08/05/20
On 08/05/2015 10:27 PM, Jamie Lennox wrote:
Hey Mike,
I think it could be one of the hacks that are in place to try and keep
compatibility with the old and new way of using the client is returning the
wrong thing. Compare the output of trustor.user_id and
trustor_auth.get_user_id(sess). For m
Let me know if that fixes it for you.
jamie
- Original Message -
> From: "michael mccune"
> To: "OpenStack Development Mailing List (not for usage questions)"
>
> Sent: Wednesday, August 5, 2015 11:37:10 PM
> Subject: Re: [openstack-dev] [keystone]
On 08/05/2015 02:34 AM, Steve Martinelli wrote:
I think this is happening because the last "session" created was based
off of trustee_auth. Try creating 2 sessions, one for each user (trustor
and trustee). Maybe Jamie will chime in.
just as a followup, i tried creating new Session objects for e
On 08/05/2015 02:34 AM, Steve Martinelli wrote:
I think this is happening because the last "session" created was based
off of trustee_auth. Try creating 2 sessions, one for each user (trustor
and trustee). Maybe Jamie will chime in.
thanks for the reply Steve, i will give that a try. my underst
M:
> From: michael mccune
> To: "OpenStack Development Mailing List (not for usage questions)"
>
> Date: 2015/08/03 07:12 PM
> Subject: [openstack-dev] [keystone] policy issues when generating
> trusts with different clients
>
> hi all,
>
> i am doing
hi all,
i am doing some work to change sahara to make greater use of
keystoneclient.session.Session objects and i am running into a strange
error when issuing the trusts.
the crux of this issue is that when i create Client objects by passing
all the parameters directly to the client, the tru
