| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
| |
This commit adds issued_at values, role IDs, and fixes endpoints
in the example data.
Change-Id: I3e2a2296d08a34331b1afd02126445d0206eea7a
|
|
|
|
| |
Change-Id: Ic408dd3935818adbef3ff4baa7c9699e4f07814e
|
|
|
|
|
|
|
|
|
|
|
|
| |
This timestamp is the last possible moment that can be represented on
32-bit systems as an integer.
As a consequence of revising the JSON examples, the corresponding PEM
files must be re-generated as well.
Change-Id: Ic6014c08b4545db036605beef1e6a8829ed347c4
Related-Bug: 1190054
Related-Bug: 1225084
|
|
|
|
|
|
|
|
|
|
|
|
| |
Explicitly checks the expiry on the tokens, and rejects tokens that
have expired
had to regenerate the sample data for the tokens as they all had been
generated with values that are now expired.
bug 1179615
Change-Id: Ie06500d446f55fd0ad67ea540c92d8cfc57483f4
|
|
This step in the process duplicates the auth-token code to keystoneclient but,
for the moment, leaves a copy in its origional location in keystone.
Testing for auth-token is also copied across, as is the cms support file.
Although no other project will yet pick up the code here in the client, since
the paste.ini files haev not yet been updated, it would work if anyone
did reference it.
Once the client code is in, the next step is to update all the other
project paste files, and then finally retire the code from keystone.
Change-Id: I88853a373d406020d54b61cba5a5e887380e3b3e
|