)]}'
{"specs/kilo/non-persistent-tokens.rst":[{"author":{"_account_id":6482,"name":"Steve Martinelli","email":"s.martinelli@gmail.com","username":"stevemar"},"change_message_id":"9a40ea39a4e05c30bc8327b5bf77aece73967793","unresolved":false,"context_lines":[{"line_number":51,"context_line":"The change will be to eliminate the need to persist tokens to any form of"},{"line_number":52,"context_line":"stable storage. When using the new non-persistent token provider, UUID and"},{"line_number":53,"context_line":"short-hashed versions of PKI tokens will not be supported. The UUID and"},{"line_number":54,"context_line":"standard PKI token providers will not be deprecated in the ``Juno`` development"},{"line_number":55,"context_line":"cycle. Deprecation of the original PKI token providers (PKI and PKIZ) will"},{"line_number":56,"context_line":"occur as early as the K cycle; this delay in deprecation allows for operators"},{"line_number":57,"context_line":"and deployers to adopt the new non-persistent tokens before it becomes the"}],"source_content_type":"text/x-rst","patch_set":1,"id":"9aa7fdbe_0e905142","line":54,"updated":"2014-10-22 03:35:41.000000000","message":"s/Juno/Kilo","commit_id":"ac77527876eef1cf45725172703a84a3402f6f66"},{"author":{"_account_id":6482,"name":"Steve Martinelli","email":"s.martinelli@gmail.com","username":"stevemar"},"change_message_id":"9a40ea39a4e05c30bc8327b5bf77aece73967793","unresolved":false,"context_lines":[{"line_number":53,"context_line":"short-hashed versions of PKI tokens will not be supported. The UUID and"},{"line_number":54,"context_line":"standard PKI token providers will not be deprecated in the ``Juno`` development"},{"line_number":55,"context_line":"cycle. Deprecation of the original PKI token providers (PKI and PKIZ) will"},{"line_number":56,"context_line":"occur as early as the K cycle; this delay in deprecation allows for operators"},{"line_number":57,"context_line":"and deployers to adopt the new non-persistent tokens before it becomes the"},{"line_number":58,"context_line":"default deployment model. The UUID token provider will be evaluated for"},{"line_number":59,"context_line":"deprecation based upon how many deployments continue to utilize UUID over PKI"}],"source_content_type":"text/x-rst","patch_set":1,"id":"9aa7fdbe_4e9a5964","line":56,"updated":"2014-10-22 03:35:41.000000000","message":"s/K/L","commit_id":"ac77527876eef1cf45725172703a84a3402f6f66"},{"author":{"_account_id":1941,"name":"Lin Hua Cheng","email":"os.lcheng@gmail.com","username":"lin-hua-cheng"},"change_message_id":"9b720177e85584679fbf48021a4dd335550317b0","unresolved":false,"context_lines":[{"line_number":56,"context_line":"occur as early as the K cycle; this delay in deprecation allows for operators"},{"line_number":57,"context_line":"and deployers to adopt the new non-persistent tokens before it becomes the"},{"line_number":58,"context_line":"default deployment model. The UUID token provider will be evaluated for"},{"line_number":59,"context_line":"deprecation based upon how many deployments continue to utilize UUID over PKI"},{"line_number":60,"context_line":"tokens."},{"line_number":61,"context_line":""},{"line_number":62,"context_line":"Alternatives"}],"source_content_type":"text/x-rst","patch_set":1,"id":"9aa7fdbe_dbd42d49","line":59,"updated":"2014-10-22 19:37:44.000000000","message":"s/PKI/non-persistent or non-persistent PKI\n\nusing the term \"PKI\" is bit confusing, made me think about the original PKI token.","commit_id":"ac77527876eef1cf45725172703a84a3402f6f66"},{"author":{"_account_id":6482,"name":"Steve Martinelli","email":"s.martinelli@gmail.com","username":"stevemar"},"change_message_id":"9a40ea39a4e05c30bc8327b5bf77aece73967793","unresolved":false,"context_lines":[{"line_number":78,"context_line":""},{"line_number":79,"context_line":"Data Model Impact"},{"line_number":80,"context_line":"-----------------"},{"line_number":81,"context_line":""},{"line_number":82,"context_line":"The general data model for the token (in-memory) will change to be a token"},{"line_number":83,"context_line":"version agnostic memory construct. This will be a departure from the current"},{"line_number":84,"context_line":"Python dictionary that is used (and varies in structure based upon token"}],"source_content_type":"text/x-rst","patch_set":1,"id":"9aa7fdbe_4eb179e0","line":81,"updated":"2014-10-22 03:35:41.000000000","message":"You can add a note here that this was completed in Juno","commit_id":"ac77527876eef1cf45725172703a84a3402f6f66"},{"author":{"_account_id":7725,"name":"David Stanek","email":"dstanek@dstanek.com","username":"dstanek"},"change_message_id":"f6e71a8047f152b5ce402ffcd2d3d666f3e6fa7b","unresolved":false,"context_lines":[{"line_number":148,"context_line":"Performance Impact"},{"line_number":149,"context_line":"------------------"},{"line_number":150,"context_line":""},{"line_number":151,"context_line":"Generally speaking this change should reduce load on the system and resource"},{"line_number":152,"context_line":"consumption by not requiring persistence of token data. Tokens will need to be"},{"line_number":153,"context_line":"decoded via CMS, raising the CPU cost of handling GET and HEAD (validate and"},{"line_number":154,"context_line":"check) mechanisms on tokens in the v2.0 Idenity API. This change is due to the"}],"source_content_type":"text/x-rst","patch_set":1,"id":"9aa7fdbe_340f0330","line":151,"updated":"2014-10-23 02:02:29.000000000","message":"Is this referring to the Keystone, the service running the middleware or both?","commit_id":"ac77527876eef1cf45725172703a84a3402f6f66"},{"author":{"_account_id":5707,"name":"Henry Nash","email":"henryn@linux.vnet.ibm.com","username":"henry-nash"},"change_message_id":"99964e2824a5bf03bc3b549864674a78ededb71c","unresolved":false,"context_lines":[{"line_number":61,"context_line":"cycle. Deprecation of the original PKI token providers (PKI and PKIZ) will"},{"line_number":62,"context_line":"occur as early as the L cycle; this delay in deprecation allows for operators"},{"line_number":63,"context_line":"and deployers to adopt the new non-persistent tokens before it becomes the"},{"line_number":64,"context_line":"default deployment model."},{"line_number":65,"context_line":""},{"line_number":66,"context_line":"Alternatives"},{"line_number":67,"context_line":"------------"}],"source_content_type":"text/x-rst","patch_set":4,"id":"5a890539_400d8a36","line":64,"updated":"2014-11-14 09:44:30.000000000","message":"We don\u0027t actually say here what the token format is for the new token provider (mush further down we learn that it is PKI).  So 1) maybe we should jus mention that here, and b) is there a reason it isn\u0027t PKIZ (given our concern over token size)?","commit_id":"02b97a891e213b744b33619141dd06ac02d78d07"},{"author":{"_account_id":2903,"name":"Morgan Fainberg","email":"morgan.fainberg@gmail.com","username":"mdrnstm"},"change_message_id":"3d6a0cbead798df70819a30fc6cc2689c3d77be6","unresolved":false,"context_lines":[{"line_number":61,"context_line":"cycle. Deprecation of the original PKI token providers (PKI and PKIZ) will"},{"line_number":62,"context_line":"occur as early as the L cycle; this delay in deprecation allows for operators"},{"line_number":63,"context_line":"and deployers to adopt the new non-persistent tokens before it becomes the"},{"line_number":64,"context_line":"default deployment model."},{"line_number":65,"context_line":""},{"line_number":66,"context_line":"Alternatives"},{"line_number":67,"context_line":"------------"}],"source_content_type":"text/x-rst","patch_set":4,"id":"5a890539_568aa61b","line":64,"in_reply_to":"5a890539_400d8a36","updated":"2014-11-14 16:54:59.000000000","message":"Done. And it will be possible to use either.","commit_id":"02b97a891e213b744b33619141dd06ac02d78d07"},{"author":{"_account_id":4,"name":"Dolph Mathews","email":"dolph.mathews@gmail.com","username":"dolph"},"change_message_id":"8b27b8d45e560567c5cbb6f376de7aa8e3103185","unresolved":false,"context_lines":[{"line_number":5,"context_line":" http://creativecommons.org/licenses/by/3.0/legalcode"},{"line_number":6,"context_line":""},{"line_number":7,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":8,"context_line":"Non-Persistent Tokens (Kilo Continuation)"},{"line_number":9,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":10,"context_line":""},{"line_number":11,"context_line":".. NOTE::"}],"source_content_type":"text/x-rst","patch_set":5,"id":"3a961159_85e60a15","line":8,"updated":"2014-12-16 21:43:33.000000000","message":"ROUND TWO","commit_id":"514da2b7f3e3ac233be3d14aa924531063ce4b0e"},{"author":{"_account_id":6460,"name":"Brad Topol","email":"btopol@us.ibm.com","username":"btopol"},"change_message_id":"327f66dd19b279347765ad113c42baa94180bb8b","unresolved":false,"context_lines":[{"line_number":45,"context_line":"  significant consumption of processing and storage resources."},{"line_number":46,"context_line":""},{"line_number":47,"context_line":"* Memcached (and largely all Key-Value-Store backends) show poor handling of"},{"line_number":48,"context_line":"  the required enumeration of each user\u0027s tokens to handle revocations under"},{"line_number":49,"context_line":"  the Token Revocation List. Even with the revocation events, the overhead"},{"line_number":50,"context_line":"  in running the backing store can be significant while providing little"},{"line_number":51,"context_line":"  added value."}],"source_content_type":"text/x-rst","patch_set":5,"id":"5a890539_3ba6acae","line":48,"updated":"2014-11-17 20:46:19.000000000","message":"Nice! Very good to make clear that Memcache had issues with token revocation","commit_id":"514da2b7f3e3ac233be3d14aa924531063ce4b0e"},{"author":{"_account_id":6460,"name":"Brad Topol","email":"btopol@us.ibm.com","username":"btopol"},"change_message_id":"327f66dd19b279347765ad113c42baa94180bb8b","unresolved":false,"context_lines":[{"line_number":56,"context_line":""},{"line_number":57,"context_line":"The change will be to eliminate the need to persist tokens to any form of"},{"line_number":58,"context_line":"stable storage. When using the new non-persistent token provider all tokens"},{"line_number":59,"context_line":"will be PKI or PKIZ; UUID and short-hashed versions of PKI(Z) tokens will no"},{"line_number":60,"context_line":"longer be supported. The UUID and standard PKI token providers will not be"},{"line_number":61,"context_line":"deprecated in the ``Kilo`` development cycle. Deprecation of the original"},{"line_number":62,"context_line":"PKI token providers (PKI and PKIZ) will occur as early as the L cycle; this"}],"source_content_type":"text/x-rst","patch_set":5,"id":"5a890539_fb0b447a","line":59,"updated":"2014-11-17 20:46:19.000000000","message":"When you say UUID tokens will no longer be supported do you mean UUID tokens are incompatible with the option of enabling no persistence of tokens or do you truely mean UUID tokens will no longer be supported at all?  If the answer is the latter, what do you expect folks like Swift (and others that love UUID tokens) to use and how do we know what you expect them to use will meet their needs?  Either way I think the sentences should be rephrased so your intentions are clear.","commit_id":"514da2b7f3e3ac233be3d14aa924531063ce4b0e"},{"author":{"_account_id":1916,"name":"Guang Yee","email":"gyee@suse.com","username":"guang-yee"},"change_message_id":"20e40f9541c98f3f6167f9d38e0bfc2acf01ca76","unresolved":false,"context_lines":[{"line_number":56,"context_line":""},{"line_number":57,"context_line":"The change will be to eliminate the need to persist tokens to any form of"},{"line_number":58,"context_line":"stable storage. When using the new non-persistent token provider all tokens"},{"line_number":59,"context_line":"will be PKI or PKIZ; UUID and short-hashed versions of PKI(Z) tokens will no"},{"line_number":60,"context_line":"longer be supported. The UUID and standard PKI token providers will not be"},{"line_number":61,"context_line":"deprecated in the ``Kilo`` development cycle. Deprecation of the original"},{"line_number":62,"context_line":"PKI token providers (PKI and PKIZ) will occur as early as the L cycle; this"}],"source_content_type":"text/x-rst","patch_set":5,"id":"5a890539_8f33def4","line":59,"updated":"2014-11-17 18:03:56.000000000","message":"s/PKI or PKIZ/PKI, PKIZ, or any form of trusted cryptographic tokens/","commit_id":"514da2b7f3e3ac233be3d14aa924531063ce4b0e"},{"author":{"_account_id":4,"name":"Dolph Mathews","email":"dolph.mathews@gmail.com","username":"dolph"},"change_message_id":"8b27b8d45e560567c5cbb6f376de7aa8e3103185","unresolved":false,"context_lines":[{"line_number":56,"context_line":""},{"line_number":57,"context_line":"The change will be to eliminate the need to persist tokens to any form of"},{"line_number":58,"context_line":"stable storage. When using the new non-persistent token provider all tokens"},{"line_number":59,"context_line":"will be PKI or PKIZ; UUID and short-hashed versions of PKI(Z) tokens will no"},{"line_number":60,"context_line":"longer be supported. The UUID and standard PKI token providers will not be"},{"line_number":61,"context_line":"deprecated in the ``Kilo`` development cycle. Deprecation of the original"},{"line_number":62,"context_line":"PKI token providers (PKI and PKIZ) will occur as early as the L cycle; this"}],"source_content_type":"text/x-rst","patch_set":5,"id":"3a961159_05b69adc","line":59,"in_reply_to":"5a890539_de7ac324","updated":"2014-12-16 21:43:33.000000000","message":"you\u0027re just forcing people to choose between non-persistent token format or persistent token format + persistent backend, not dropping support for UUID","commit_id":"514da2b7f3e3ac233be3d14aa924531063ce4b0e"},{"author":{"_account_id":2903,"name":"Morgan Fainberg","email":"morgan.fainberg@gmail.com","username":"mdrnstm"},"change_message_id":"1f2782595afd98d50dc7855c56ba323632e66a1c","unresolved":false,"context_lines":[{"line_number":56,"context_line":""},{"line_number":57,"context_line":"The change will be to eliminate the need to persist tokens to any form of"},{"line_number":58,"context_line":"stable storage. When using the new non-persistent token provider all tokens"},{"line_number":59,"context_line":"will be PKI or PKIZ; UUID and short-hashed versions of PKI(Z) tokens will no"},{"line_number":60,"context_line":"longer be supported. The UUID and standard PKI token providers will not be"},{"line_number":61,"context_line":"deprecated in the ``Kilo`` development cycle. Deprecation of the original"},{"line_number":62,"context_line":"PKI token providers (PKI and PKIZ) will occur as early as the L cycle; this"}],"source_content_type":"text/x-rst","patch_set":5,"id":"5a890539_de7ac324","line":59,"in_reply_to":"5a890539_fb0b447a","updated":"2014-11-19 01:21:03.000000000","message":"It is the former, not the latter.  UUID tokens cannot be supported in non-persistence-mode. The next sentence should help clarify.","commit_id":"514da2b7f3e3ac233be3d14aa924531063ce4b0e"},{"author":{"_account_id":6460,"name":"Brad Topol","email":"btopol@us.ibm.com","username":"btopol"},"change_message_id":"327f66dd19b279347765ad113c42baa94180bb8b","unresolved":false,"context_lines":[{"line_number":62,"context_line":"PKI token providers (PKI and PKIZ) will occur as early as the L cycle; this"},{"line_number":63,"context_line":"delay in deprecation allows for operators and deployers to adopt the new"},{"line_number":64,"context_line":"non-persistent tokens."},{"line_number":65,"context_line":""},{"line_number":66,"context_line":"Alternatives"},{"line_number":67,"context_line":"------------"},{"line_number":68,"context_line":""}],"source_content_type":"text/x-rst","patch_set":5,"id":"5a890539_fb8264c6","line":65,"updated":"2014-11-17 20:46:19.000000000","message":"Here there is no mention of when UUID deprecation may occur yet you do say when PKI would be deprecated.  Can you provide some insight on the future fate of UUID?  Will it always be around? Will it be deprecated when some contraints are met?  Enquiring minds want to know.","commit_id":"514da2b7f3e3ac233be3d14aa924531063ce4b0e"},{"author":{"_account_id":4,"name":"Dolph Mathews","email":"dolph.mathews@gmail.com","username":"dolph"},"change_message_id":"8b27b8d45e560567c5cbb6f376de7aa8e3103185","unresolved":false,"context_lines":[{"line_number":62,"context_line":"PKI token providers (PKI and PKIZ) will occur as early as the L cycle; this"},{"line_number":63,"context_line":"delay in deprecation allows for operators and deployers to adopt the new"},{"line_number":64,"context_line":"non-persistent tokens."},{"line_number":65,"context_line":""},{"line_number":66,"context_line":"Alternatives"},{"line_number":67,"context_line":"------------"},{"line_number":68,"context_line":""}],"source_content_type":"text/x-rst","patch_set":5,"id":"3a961159_c5dad216","line":65,"in_reply_to":"5a890539_5e8ed328","updated":"2014-12-16 21:43:33.000000000","message":"i think you need to rewrite the \"UUID ... tokens will no longer be supported\" sentence to make it clear that they will simply not be supported without a persistence backend. they\u0027re not compatible with the goals of this spec.","commit_id":"514da2b7f3e3ac233be3d14aa924531063ce4b0e"},{"author":{"_account_id":2903,"name":"Morgan Fainberg","email":"morgan.fainberg@gmail.com","username":"mdrnstm"},"change_message_id":"1f2782595afd98d50dc7855c56ba323632e66a1c","unresolved":false,"context_lines":[{"line_number":62,"context_line":"PKI token providers (PKI and PKIZ) will occur as early as the L cycle; this"},{"line_number":63,"context_line":"delay in deprecation allows for operators and deployers to adopt the new"},{"line_number":64,"context_line":"non-persistent tokens."},{"line_number":65,"context_line":""},{"line_number":66,"context_line":"Alternatives"},{"line_number":67,"context_line":"------------"},{"line_number":68,"context_line":""}],"source_content_type":"text/x-rst","patch_set":5,"id":"5a890539_5e8ed328","line":65,"in_reply_to":"5a890539_fb8264c6","updated":"2014-11-19 01:21:03.000000000","message":"UUID is not planned for deprecation, this is why it is not listed. I don\u0027t know if we want to deprecate UUID at all. I expect deprecation will be a special beast when it comes to UUID only because of how easy uuid is to work with (and in devstack).","commit_id":"514da2b7f3e3ac233be3d14aa924531063ce4b0e"},{"author":{"_account_id":1916,"name":"Guang Yee","email":"gyee@suse.com","username":"guang-yee"},"change_message_id":"20e40f9541c98f3f6167f9d38e0bfc2acf01ca76","unresolved":false,"context_lines":[{"line_number":101,"context_line":"the SQL token backend\u0027s schema to eliminate the need for a DB migration. Other"},{"line_number":102,"context_line":"token persistence backends will do in-place (seamless) handling of the"},{"line_number":103,"context_line":"differing token-formats. The persistence backend changes are required for"},{"line_number":104,"context_line":"a seamless upgrade path to non-persistent tokens."},{"line_number":105,"context_line":""},{"line_number":106,"context_line":"JSON Schema for each token version will need to be developed for complete"},{"line_number":107,"context_line":"validation as part of the conversion from the versioned-token-format to the"}],"source_content_type":"text/x-rst","patch_set":5,"id":"5a890539_4fc73696","line":104,"updated":"2014-11-17 18:03:56.000000000","message":"watch out for rolling upgrade scenario where old code need to work with new schema. Don\u0027t think we are capable of rolling upgrade right now, but something to consider if and when we do.","commit_id":"514da2b7f3e3ac233be3d14aa924531063ce4b0e"},{"author":{"_account_id":6460,"name":"Brad Topol","email":"btopol@us.ibm.com","username":"btopol"},"change_message_id":"327f66dd19b279347765ad113c42baa94180bb8b","unresolved":false,"context_lines":[{"line_number":101,"context_line":"the SQL token backend\u0027s schema to eliminate the need for a DB migration. Other"},{"line_number":102,"context_line":"token persistence backends will do in-place (seamless) handling of the"},{"line_number":103,"context_line":"differing token-formats. The persistence backend changes are required for"},{"line_number":104,"context_line":"a seamless upgrade path to non-persistent tokens."},{"line_number":105,"context_line":""},{"line_number":106,"context_line":"JSON Schema for each token version will need to be developed for complete"},{"line_number":107,"context_line":"validation as part of the conversion from the versioned-token-format to the"}],"source_content_type":"text/x-rst","patch_set":5,"id":"5a890539_7b767407","line":104,"in_reply_to":"5a890539_4fc73696","updated":"2014-11-17 20:46:19.000000000","message":"+++ Good point!","commit_id":"514da2b7f3e3ac233be3d14aa924531063ce4b0e"},{"author":{"_account_id":1916,"name":"Guang Yee","email":"gyee@suse.com","username":"guang-yee"},"change_message_id":"20e40f9541c98f3f6167f9d38e0bfc2acf01ca76","unresolved":false,"context_lines":[{"line_number":110,"context_line":"REST API Impact"},{"line_number":111,"context_line":"---------------"},{"line_number":112,"context_line":""},{"line_number":113,"context_line":"When the new provider is used (non-persistent-token-provider) only PKI tokens"},{"line_number":114,"context_line":"will be issued, and the short-hash version of the token cannot be used to"},{"line_number":115,"context_line":"interact with Keystone."},{"line_number":116,"context_line":""}],"source_content_type":"text/x-rst","patch_set":5,"id":"5a890539_0f41ae0a","line":113,"updated":"2014-11-17 18:03:56.000000000","message":"when limit to PKI, what about AE?","commit_id":"514da2b7f3e3ac233be3d14aa924531063ce4b0e"},{"author":{"_account_id":2903,"name":"Morgan Fainberg","email":"morgan.fainberg@gmail.com","username":"mdrnstm"},"change_message_id":"1f2782595afd98d50dc7855c56ba323632e66a1c","unresolved":false,"context_lines":[{"line_number":110,"context_line":"REST API Impact"},{"line_number":111,"context_line":"---------------"},{"line_number":112,"context_line":""},{"line_number":113,"context_line":"When the new provider is used (non-persistent-token-provider) only PKI tokens"},{"line_number":114,"context_line":"will be issued, and the short-hash version of the token cannot be used to"},{"line_number":115,"context_line":"interact with Keystone."},{"line_number":116,"context_line":""}],"source_content_type":"text/x-rst","patch_set":5,"id":"5a890539_1ec36b39","line":113,"in_reply_to":"5a890539_0f41ae0a","updated":"2014-11-19 01:21:03.000000000","message":"AE will be a different provider. This is specifically targeting PKI/PKIZ. AE has it\u0027s own spec.","commit_id":"514da2b7f3e3ac233be3d14aa924531063ce4b0e"},{"author":{"_account_id":6460,"name":"Brad Topol","email":"btopol@us.ibm.com","username":"btopol"},"change_message_id":"327f66dd19b279347765ad113c42baa94180bb8b","unresolved":false,"context_lines":[{"line_number":114,"context_line":"will be issued, and the short-hash version of the token cannot be used to"},{"line_number":115,"context_line":"interact with Keystone."},{"line_number":116,"context_line":""},{"line_number":117,"context_line":"REST APIs that deal directly with the token resource will be modified:"},{"line_number":118,"context_line":""},{"line_number":119,"context_line":"* V2.0 Token APIs will return a TokenNotFound (HTTP 404) if the short-hash-id"},{"line_number":120,"context_line":"  is used. This will impact HTTP GET, HEAD, and DELETE for token APIs"}],"source_content_type":"text/x-rst","patch_set":5,"id":"5a890539_5b87f8b4","line":117,"updated":"2014-11-17 20:46:19.000000000","message":"Is this breaking backward compatibility?  Need to be clear why the changes below are necessary and also if this does or does not break backward compatibility","commit_id":"514da2b7f3e3ac233be3d14aa924531063ce4b0e"},{"author":{"_account_id":2903,"name":"Morgan Fainberg","email":"morgan.fainberg@gmail.com","username":"mdrnstm"},"change_message_id":"1f2782595afd98d50dc7855c56ba323632e66a1c","unresolved":false,"context_lines":[{"line_number":114,"context_line":"will be issued, and the short-hash version of the token cannot be used to"},{"line_number":115,"context_line":"interact with Keystone."},{"line_number":116,"context_line":""},{"line_number":117,"context_line":"REST APIs that deal directly with the token resource will be modified:"},{"line_number":118,"context_line":""},{"line_number":119,"context_line":"* V2.0 Token APIs will return a TokenNotFound (HTTP 404) if the short-hash-id"},{"line_number":120,"context_line":"  is used. This will impact HTTP GET, HEAD, and DELETE for token APIs"}],"source_content_type":"text/x-rst","patch_set":5,"id":"5a890539_def64390","line":117,"in_reply_to":"5a890539_5b87f8b4","updated":"2014-11-19 01:21:03.000000000","message":"This should not break any compatibility - EXCEPT - that the short-hashed token IDs will not work.\n\nThis is an issue for Horizon, but that is why this is an optional provider to start with. And why deprecation of the other PKI providers will not occur until L at least.","commit_id":"514da2b7f3e3ac233be3d14aa924531063ce4b0e"},{"author":{"_account_id":6486,"name":"Brant Knudson","email":"blk@acm.org","username":"blk-u"},"change_message_id":"f84fb6da0486e0b7cc684364aea4cb22dbc9c42e","unresolved":false,"context_lines":[{"line_number":131,"context_line":"Security Impact"},{"line_number":132,"context_line":"---------------"},{"line_number":133,"context_line":""},{"line_number":134,"context_line":"The internal token format will be changed to be consistent. Externally facing"},{"line_number":135,"context_line":"use and format of the token should not be impacted."},{"line_number":136,"context_line":""},{"line_number":137,"context_line":"All cases of PKI tokens will be decoded (in a similar fashion to auth_token"}],"source_content_type":"text/x-rst","patch_set":5,"id":"3a961159_230b2ad6","line":134,"updated":"2015-01-15 00:28:09.000000000","message":"both this spec and AE tokens require the internal token format to change. If both are approved we need to pick one that works for both. I think the work to make the token format consistent should be moved to a separate spec.\n\nAlso, I think the token format chosen should be the AE format.\n\nAlso, this isn\u0027t a security impact.","commit_id":"514da2b7f3e3ac233be3d14aa924531063ce4b0e"},{"author":{"_account_id":6486,"name":"Brant Knudson","email":"blk@acm.org","username":"blk-u"},"change_message_id":"f84fb6da0486e0b7cc684364aea4cb22dbc9c42e","unresolved":false,"context_lines":[{"line_number":138,"context_line":"middleware) in memory instead of referencing data stored in the token DB"},{"line_number":139,"context_line":"persistence store. The ability to use the token backend for auditing will no"},{"line_number":140,"context_line":"longer be available. Instead audit will rely exclusively on the ``CADF``"},{"line_number":141,"context_line":"authentication notifications."},{"line_number":142,"context_line":""},{"line_number":143,"context_line":""},{"line_number":144,"context_line":"Notifications Impact"}],"source_content_type":"text/x-rst","patch_set":5,"id":"3a961159_831cde14","line":141,"updated":"2015-01-15 00:28:09.000000000","message":"I don\u0027t see how this is a security impact.","commit_id":"514da2b7f3e3ac233be3d14aa924531063ce4b0e"},{"author":{"_account_id":6486,"name":"Brant Knudson","email":"blk@acm.org","username":"blk-u"},"change_message_id":"f84fb6da0486e0b7cc684364aea4cb22dbc9c42e","unresolved":false,"context_lines":[{"line_number":230,"context_line":"    token-provider-cleanup.html\u003e`_"},{"line_number":231,"context_line":""},{"line_number":232,"context_line":"*   This spec depends on full revocation event support in auth_token"},{"line_number":233,"context_line":"    middleware."},{"line_number":234,"context_line":""},{"line_number":235,"context_line":""},{"line_number":236,"context_line":"Testing"}],"source_content_type":"text/x-rst","patch_set":5,"id":"3a961159_23d96a56","line":233,"updated":"2015-01-15 00:28:09.000000000","message":"where\u0027s the spec for that?","commit_id":"514da2b7f3e3ac233be3d14aa924531063ce4b0e"}]}
