delta/openstack/python-keystoneclient.git/keystoneclient/tests/unit/v3, branch 3.8.0

Merge "Fix missing service_catalog parameter in Client object"

2016-12-01T00:08:44+00:00

Merge "Pass allow_expired to token validate"

2016-11-29T23:02:41+00:00

Pass allow_expired to token validate

2016-11-29T21:23:28+00:00

Allow passing the allow_expired flag to v3 token validation to support
extended service to service communication.

Implements bp: allow-expired
Change-Id: Ia1763fedc1838ad3c58c7f8f98f00b7eaad55a5c

Replace 'assertFalse(a in b)' with 'assertNotIn(a, b)'

2016-11-18T02:56:54+00:00

Trivial fix.

Change-Id: I818245eaa9e63322b1c6de049368aa4e09b01b4b

Support domain-specific configuration management

2016-11-02T17:03:41+00:00

Provide support for the domain-specific configuration storage available
via the REST API.

Domain configs are JSON blobs and we have fine grained control on them
via the Identity API. This fine grained control is not defined yet in the
client, though - for now, we can manage everything like Python dictionaries
and use operations like "update" whenever we want to delete a specific group
or option. This approach is similar to what is done in the federation mapping
API to handle mapping rules.

Functional tests are also included, this is useful to check if the new
feature works in an integration environment.

Co-Auhtored-By: Henry Nash 
Co-Authored-By: Rodrigo Duarte 

Closes-Bug: 1433306

Partially Implements: blueprint domain-config-ext

Change-Id: Ie6795b8633fed38c58b79250c11c9a045b7f95a4

Merge "Use exceptions from Keystoneauth"

2016-10-14T14:10:27+00:00

Merge "Use fixtures from keystoneauth"

2016-10-05T21:48:44+00:00

Correct output for Implied Roles

2016-09-21T15:04:37+00:00

Change-Id: I66e863fb83f8dfcca2c48116d4377df060f402c3
Closes-Bug: 1622346

Use exceptions from Keystoneauth

2016-08-24T08:52:36+00:00

As keystoneclient and other services rely more on keystoneauth we should
assume that keystoneauth is our base auth library, not keystoneclient
and start to default to the objects provided from there. This will make
it easier to remove these objects when the time comes.

For the session independant parts of keystoneclient we should use the
exception names as provided by keystoneauth instead of the aliases in
keystoneclient.

Change-Id: Ic513046f8398a76c244e145d6cc3117cdf6bb4cd

Use fixtures from keystoneauth

2016-08-24T08:52:27+00:00

As keystoneclient and other services rely more on keystoneauth we should
assume that keystoneauth is our base auth library, not keystoneclient
and start to default to the objects provided from there. This will make
it easier to remove these objects when the time comes.

The easiest thing to move is the keystoneclient fixtures in favor of the
keystoneauth fixtures.

Change-Id: I5a784795536cec6c7ca5eead3f13b1e7a6e45346