)]}'
{"api/v3/identity-api-v3-token-formats.md":[{"author":{"_account_id":5046,"name":"Lance Bragstad","email":"lbragstad@redhat.com","username":"ldbragst"},"change_message_id":"574a023becc0ca2a35c22420194af924307a6f99","unresolved":false,"context_lines":[{"line_number":12,"context_line":"## UUID Tokens"},{"line_number":13,"context_line":"A UUID token is the oldest format, and has no identifying data in it."},{"line_number":14,"context_line":"A UUID token looks like this:"},{"line_number":15,"context_line":""},{"line_number":16,"context_line":"e60191a29486420f96b7d660a5421aab"},{"line_number":17,"context_line":""},{"line_number":18,"context_line":"## ASN1 Tokens"}],"source_content_type":"text/x-markdown","patch_set":1,"id":"3a961159_2bda204c","line":15,"updated":"2014-12-19 15:02:30.000000000","message":"Is list intended to outline the details of each format? Pros? Cons?","commit_id":"7702693363b7d44fb52c4757a142717368ad5903"},{"author":{"_account_id":5046,"name":"Lance Bragstad","email":"lbragstad@redhat.com","username":"ldbragst"},"change_message_id":"574a023becc0ca2a35c22420194af924307a6f99","unresolved":false,"context_lines":[{"line_number":15,"context_line":""},{"line_number":16,"context_line":"e60191a29486420f96b7d660a5421aab"},{"line_number":17,"context_line":""},{"line_number":18,"context_line":"## ASN1 Tokens"},{"line_number":19,"context_line":"The first form of tokens to contain a format identifier are tokens that contain"},{"line_number":20,"context_line":"all of the data from the token validation response.  The JSON document is"},{"line_number":21,"context_line":"converted into a Crypto Message Syntax (CMS) encoded document which is base64"}],"source_content_type":"text/x-markdown","patch_set":1,"id":"3a961159_4bb20c07","line":18,"updated":"2014-12-19 15:02:30.000000000","message":"ASN1 -\u003e PKI","commit_id":"7702693363b7d44fb52c4757a142717368ad5903"},{"author":{"_account_id":5046,"name":"Lance Bragstad","email":"lbragstad@redhat.com","username":"ldbragst"},"change_message_id":"574a023becc0ca2a35c22420194af924307a6f99","unresolved":false,"context_lines":[{"line_number":30,"context_line":""},{"line_number":31,"context_line":"## PKIZ"},{"line_number":32,"context_line":""},{"line_number":33,"context_line":"The Data encoded in the token quickly expanded to sizes that were impractical to transmit in headers.  The first attempt to minimize the token size was to compress the tokens.  To distinguish these tokens from the earlier format, the format identifier `PKIZ` is prepended to these tokens."},{"line_number":34,"context_line":""},{"line_number":35,"context_line":""},{"line_number":36,"context_line":"# Token Naming conventions"}],"source_content_type":"text/x-markdown","patch_set":1,"id":"3a961159_4ba92c8f","line":33,"updated":"2014-12-19 15:02:30.000000000","message":"over 80 characters.","commit_id":"7702693363b7d44fb52c4757a142717368ad5903"},{"author":{"_account_id":5046,"name":"Lance Bragstad","email":"lbragstad@redhat.com","username":"ldbragst"},"change_message_id":"574a023becc0ca2a35c22420194af924307a6f99","unresolved":false,"context_lines":[{"line_number":41,"context_line":"The following prefix identifies the token as an OpenStack Identity API"},{"line_number":42,"context_line":"Authorization token."},{"line_number":43,"context_line":""},{"line_number":44,"context_line":"`OSAUTHZ`"},{"line_number":45,"context_line":""},{"line_number":46,"context_line":"The next 4 characters will be the Hexidecimal representation of the token format.  Thus the formats will range from"},{"line_number":47,"context_line":""}],"source_content_type":"text/x-markdown","patch_set":1,"id":"3a961159_cb735c4c","line":44,"updated":"2014-12-19 15:02:30.000000000","message":"what else would need to know this about a token that we create? \n\nsince Keystone is creating and validating the tokens, I don\u0027t think that we need to have `OSAUTHZ` prefixing the token. A token type and token version should work. Which can be done with 4 characters.","commit_id":"7702693363b7d44fb52c4757a142717368ad5903"}]}
