When the server converted a V2 token to a V3 token it regenerated
the issued_at time.
This was causing the server to return a different issued_at time
when a V2 token was validated using the V3 API.
This was causing the server to fail to revoke a V2 token if it was
revoked before validating it first because the regenerated token was
considered to be after the revocation event.
Change-Id: I71fea3253295ee8794fb2c8211e1f030de3ae205
Closes-Bug: #1348820
(cherry picked from commit a4c73e4382cb062aa9f30fe1960d5014d3c49cc2)
Reviewed: https:/ /review. openstack. org/111772 /git.openstack. org/cgit/ openstack/ keystone/ commit/ ?id=bdb88c662ac 2035f9b0d8a229a 5db5f60f5f16ae
Committed: https:/
Submitter: Jenkins
Branch: stable/icehouse
commit bdb88c662ac2035 f9b0d8a229a5db5 f60f5f16ae
Author: Brant Knudson <email address hidden>
Date: Fri Jul 25 16:26:38 2014 -0500
Fix for V2 token issued_at time changing
When the server converted a V2 token to a V3 token it regenerated
the issued_at time.
This was causing the server to return a different issued_at time
when a V2 token was validated using the V3 API.
This was causing the server to fail to revoke a V2 token if it was
revoked before validating it first because the regenerated token was
considered to be after the revocation event.
Change-Id: I71fea3253295ee 8794fb2c8211e1f 030de3ae205 aa9f30fe1960d50 14d3c49cc2)
Closes-Bug: #1348820
(cherry picked from commit a4c73e4382cb062