delta/openstack/python-keystoneclient.git/examples/pki/cms/revocation_list.json, branch stable/kilo

Add data to example data

2015-02-09T19:01:40+00:00

This commit adds issued_at values, role IDs, and fixes endpoints
in the example data.

Change-Id: I3e2a2296d08a34331b1afd02126445d0206eea7a

Example JSON files should be human-readable

2014-07-22T15:50:21+00:00

Change-Id: Ic408dd3935818adbef3ff4baa7c9699e4f07814e

Compressed Signature and Validation

2014-05-09T18:48:17+00:00

Allows for a new form of document signature.

pkiz_sign will take data and encode it in a string that starts with
the substring  "PKIZ_".  This prefix indicates that the data has been:
1) Signed via PKI in Crypto Message Syntax (CMS) in binary (DER) format
2) Compressed using zlib (comparable to gzip)
3) urlsafe-base64 decoded

This process is reversed to validate the data.

middleware/auth_token.py will be capable of validating Keystone
tokens that are marshalled in the new format.  The current existing
"PKI" tokens will continue to be identified with "MII", issued by
default, and validated as well.  It will require corresponding changes
on the Keystone server to issue the new token format.

A separate script for generating the sample
data used in the unit tests,
examples/pki/gen_cmsz.py,
also serves as an example of how to
call the API from Python code.

Some of the sample data for the old tests had to be regenerated. A
stray comma in one of the JSON files made for non-parsing JSON.

Blueprint: compress-tokens
Closes-Bug: #1255321

Change-Id: Ia9a66ba3742da0bcd58c4c096b28cc8a66ad6569

Add auth-token code to keystoneclient, along with supporting files

2012-11-12T19:40:21+00:00

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