<feed xmlns='http://www.w3.org/2005/Atom'>
<title>delta/openstack/python-keystoneclient.git/examples/pki/cms/auth_token_revoked.json, branch juno-eol</title>
<subtitle>opendev.org: openstack/python-keystoneclient.git
</subtitle>
<link rel='alternate' type='text/html' href='http://91.123.203.49/cgit/delta/openstack/python-keystoneclient.git/'/>
<entry>
<title>Example JSON files should be human-readable</title>
<updated>2014-07-22T15:50:21+00:00</updated>
<author>
<name>Harry Rybacki</name>
<email>hrybacki@redhat.com</email>
</author>
<published>2014-07-19T21:32:31+00:00</published>
<link rel='alternate' type='text/html' href='http://91.123.203.49/cgit/delta/openstack/python-keystoneclient.git/commit/?id=b178fccb732c93f254bed0c7e66e8e0ee4280de9'/>
<id>b178fccb732c93f254bed0c7e66e8e0ee4280de9</id>
<content type='text'>
Change-Id: Ic408dd3935818adbef3ff4baa7c9699e4f07814e
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Change-Id: Ic408dd3935818adbef3ff4baa7c9699e4f07814e
</pre>
</div>
</content>
</entry>
<entry>
<title>Set example timestamps to 2038-01-18T21:14:07Z</title>
<updated>2013-09-13T16:43:35+00:00</updated>
<author>
<name>Dolph Mathews</name>
<email>dolph.mathews@gmail.com</email>
</author>
<published>2013-09-13T16:29:49+00:00</published>
<link rel='alternate' type='text/html' href='http://91.123.203.49/cgit/delta/openstack/python-keystoneclient.git/commit/?id=2fdbcbd06cfa6fd4348bc3752554331651717c87'/>
<id>2fdbcbd06cfa6fd4348bc3752554331651717c87</id>
<content type='text'>
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
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
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
</pre>
</div>
</content>
</entry>
<entry>
<title>Check Expiry</title>
<updated>2013-05-28T14:47:54+00:00</updated>
<author>
<name>Adam Young</name>
<email>ayoung@redhat.com</email>
</author>
<published>2013-05-28T13:50:51+00:00</published>
<link rel='alternate' type='text/html' href='http://91.123.203.49/cgit/delta/openstack/python-keystoneclient.git/commit/?id=8fe7a822d3fd9f435bb4a73a838b380659196cf7'/>
<id>8fe7a822d3fd9f435bb4a73a838b380659196cf7</id>
<content type='text'>
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
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
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
</pre>
</div>
</content>
</entry>
<entry>
<title>Add auth-token code to keystoneclient, along with supporting files</title>
<updated>2012-11-12T19:40:21+00:00</updated>
<author>
<name>Henry Nash</name>
<email>henryn@linux.vnet.ibm.com</email>
</author>
<published>2012-11-12T19:40:21+00:00</published>
<link rel='alternate' type='text/html' href='http://91.123.203.49/cgit/delta/openstack/python-keystoneclient.git/commit/?id=7920899af119d1697c333d202ca3272f167c19b0'/>
<id>7920899af119d1697c333d202ca3272f167c19b0</id>
<content type='text'>
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
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
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
</pre>
</div>
</content>
</entry>
</feed>
