yahoo-eng-team team mailing list archive

[Morgan Fainberg <morgan.fainberg@xxxxxxxxx>]

This is more new functionality than a bug fix. V2 largely is viewed as
frozen, we should not be adding (or removing) functionality to it. Since
this is not an issue with V3, if the workflow requires username/password
direct to the trust token, it is recommended that V3 be used instead.

** Changed in: keystone
       Status: In Progress => Won't Fix

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Keystone.
https://bugs.launchpad.net/bugs/1331884

Title:
  A V2 token from trust cannot be generated with user/pass

Status in OpenStack Identity (Keystone):
  Won't Fix

Bug description:
  Trust handling in the v2 authentication path only exists for token
  authentication. That means you must fetch a token with your user/pass
  and then exchange that for one that is trusted.

  Example workflow:

  c2_1 = v2client.Client(auth_url='http://localhost:5000/v2.0',
                         username='bob',
                         password='bob1',
                         trust_id='0b16de31a8c64fd5b0054054db468a00')

  c2_2 = v2client.Client(auth_url='http://localhost:5000/v2.0',
                         token=c2_1.auth_ref.auth_token,
                         tenant_name='demo',
                         trust_id='0b16de31a8c64fd5b0054054db468a00')

  As compared to v3:

  c3 = v3client.Client(auth_url='http://localhost:5000/v3',
                       username='bob',
                       password='bob1',
                       trust_id='0b16de31a8c64fd5b0054054db468a00')

To manage notifications about this bug go to:
https://bugs.launchpad.net/keystone/+bug/1331884/+subscriptions