{"push_id":1343872719,"size":1,"distinct_size":1,"ref":"refs/heads/master","head":"074d810a03a2a3e1504adce3dfa337636550e0a2","before":"f9ad3e5e062844971a57945a319ca573ab49f0cf","commits":[{"sha":"074d810a03a2a3e1504adce3dfa337636550e0a2","author":{"name":"Jenkins","email":"61eb39d4445155efb6068840385577c11776cd20@review.openstack.org"},"message":"Updated openstack/openstack\nProject: openstack/keystone  f6509955b923e1d9a1639c746f2883b9b0d6f9d3\n\nMake sure all v3 tokens are validated the same way\n\nSome token formats require persistence (uuid, pki, pkiz) while\nothers don't (fernet). Persistent tokens were typically validated\nby returning the token reference as it was constructed at creation\ntime, essentially returning a cached version of the token.\nNon-persistent tokens formats are unable to do this because they are\nnot stored anywhere (exactly as the name implies). This means the\ntoken reference must be rebuilt from scratch every time a\nnon-persistent token is validated. The advantage of this approach\nis that less revocation events are needed and token data is considered\naccurate at validation time.\n\nThis commit makes it so that all token formats issuing v3 tokens\nvalidate tokens by reconstructing them, instead of relying on\npossibly stale data from creation time.\n\nChange-Id: I9584ce9627a91666f4dba62eb46e593f2053193b","distinct":true,"url":"https://api.github.com/repos/openstack/openstack/commits/074d810a03a2a3e1504adce3dfa337636550e0a2"}]}
{"actor":{"display_login":"openstack-gerrit"}}