summaryrefslogtreecommitdiff
path: root/keystoneclient/fixture
Commit message (Collapse)AuthorAgeFilesLines
* Correct documenting constructor parametersBrant Knudson2014-12-041-37/+29
| | | | | | | | | | When the docs are rendered to HTML, any docs on __init__ are not displayed. The parameters to the constructor have to be documented on the class rather than on the __init__ method. Also, corrected other minor issues in the same areas. Change-Id: Ic56da33f6b99fe5efb636c289e3c4e1569f0c84c
* Use oslo.utils and oslo.serializationSteve Martinelli2014-10-153-3/+6
| | | | | | | Left timeutils and strutils in openstack/common since they are used in openstack/common/apiclient and memorycache. Change-Id: Idb5f09c159d907dfba84cd1f7501f650318af7d9
* Handle federated tokensMarek Denis2014-09-172-0/+30
| | | | | | | | | | | | | Federated tokens don't include domains in the user object. Keystoneclient should be able to estimate whether the token is a federated one and, if so, don't expect user domain information. In case of the federated token keystoneclient returns None in response to user_domain_name and user_domain_id calls. Co-Authored-By: Steve Martinelli <stevemar@ca.ibm.com> Closes-Bug: #1346820 Change-Id: I3453275fa1b0a41b1c015b0c3a92895a77d69a41
* fix typosDolph Mathews2014-09-081-1/+1
| | | | Change-Id: Ia850e62fe4c888365f5031cc8b7c7ad526600222
* Fix mistakes in token fixturesJamie Lennox2014-07-162-2/+2
| | | | | | | | | There are two small mistakes i discovered in the token fixtures. Fix these and add a bunch of new tests that would have caught them earlier. Closes-Bug: #1342513 Closes-Bug: #1342515 Change-Id: I7c07bd915fd84cc77cae0004220d8bb8d79bb082
* Merge "Add trust users to AccessInfo and fixture"Jenkins2014-07-111-1/+27
|\
| * Add trust users to AccessInfo and fixtureJamie Lennox2014-06-291-1/+27
| | | | | | | | | | | | | | A trust should always contain a trustee_user_id and a trustor_user_id. Expose these values via AccessInfo if available. Change-Id: Ic46a44300e6bf8aa694f1543d470c16fcac643fc
* | Merge "Add OAuth data to AccessInfo"Jenkins2014-07-091-1/+26
|\ \ | |/
| * Add OAuth data to AccessInfoJamie Lennox2014-06-301-1/+26
| | | | | | | | | | | | | | | | | | Allow access to the access_token_id and the consumer_id that are set as part of the Oauth authentication process. This only makes sense for V3 tokens, as Oauth cannot be used with v2. Change-Id: I9ac76f92acdfd6446a13f535b24e0a99f02f2eef
* | Add a fixture for Keystone version discoveryJamie Lennox2014-07-022-3/+277
|/ | | | | | | | As we push out the session and expect people to test with proper URL responses we should provide a means to create a correct Keystone version list to test with. Change-Id: I8309ab6cbc47ad159f3c6e018b60ff8c15c6d917
* Add issued handlers to auth_ref and fixturesJamie Lennox2014-06-192-6/+55
| | | | | | | | issued_at is a standard part of V2 and V3 tokens so add it to AccessInfo in a similar way to expiry. Also it should be included when generating tokens so include it in fixtures. Change-Id: I0d62d8ce6472466886751e10e98046b8e398e079
* Add role ids to the AccessInfoJamie Lennox2014-06-191-4/+9
| | | | | | Role Names are already there, add ids as well. Change-Id: Ie6f14a60b182ec2f4ab97c6ced564e63a2f5169a
* Create a V3 Token GeneratorJamie Lennox2014-04-172-1/+306
| | | | | | | | A token generator that can be used by other clients to generate consistent tokens in there test code. Change-Id: I05d2632b4c8290c2b1015996769340f0bea16f93 blueprint: share-tokens
* Don't use generic kwargs in v2 Token GenerationJamie Lennox2014-04-141-23/+22
| | | | | | | | | | | We need to allow for people adding other stuff to the tokens however it shouldn't be available in the standard case where for example a misspelt variable would be propagated. This is in line with how v3 is going to handle this same scenario. Change-Id: I1aad17893574ebc7c3a6b84f4d6ba1cd27932158 Closes-Bug: #1307278
* Create a test token generator and use itJamie Lennox2014-04-033-0/+207
All the clients are currently storing samples of keystone tokens so that they can use them in testing. This is bad as they are often out of date or contain data that they shouldn't. Create a V2 Token generator and make use of that for generating tokens within our tests. Change-Id: I72928692142c967d13391752ba57b3bdf7c1feab blueprint: share-tokens