)]}'
{"specs/backlog/decouple-auth-from-api-version.rst":[{"author":{"_account_id":6460,"name":"Brad Topol","email":"btopol@us.ibm.com","username":"btopol"},"change_message_id":"43c161c36b43f952ddcd608f98f66b1ae08dc852","unresolved":false,"context_lines":[{"line_number":27,"context_line":"be an improvement to move to a ``/auth`` location to handle all authentication"},{"line_number":28,"context_line":"requests."},{"line_number":29,"context_line":""},{"line_number":30,"context_line":"This has the added benefit of decoupling authentication responses from a"},{"line_number":31,"context_line":"specific API version. If an auth change is desired, the contract in data"},{"line_number":32,"context_line":"returned is not locked in as it is today, a new auth version can be created"},{"line_number":33,"context_line":"without changing the Keystone CRUD API, since auth is now decoupled."}],"source_content_type":"text/x-rst","patch_set":1,"id":"3afb71cf_0440d932","line":30,"updated":"2015-06-10 19:45:58.000000000","message":"This would be an outstanding improvement!","commit_id":"07653211dfc6373768d02d4c79c4c7c1cf91105e"},{"author":{"_account_id":6460,"name":"Brad Topol","email":"btopol@us.ibm.com","username":"btopol"},"change_message_id":"43c161c36b43f952ddcd608f98f66b1ae08dc852","unresolved":false,"context_lines":[{"line_number":61,"context_line":"  having requirements to utilize resources under ``OS-FEDERATION``."},{"line_number":62,"context_line":""},{"line_number":63,"context_line":"The current auth locations would be wired up on the backend to the new auth"},{"line_number":64,"context_line":"system to ensure there is only 1 path authentication travels through. The"},{"line_number":65,"context_line":"old locations for authentication will be deprecated (but no plans for removal)"},{"line_number":66,"context_line":"until the whole API is deprecated (e.g. when V2.0 is removed, the"},{"line_number":67,"context_line":"``/v2.0/tokens`` location will be removed, but not before)."}],"source_content_type":"text/x-rst","patch_set":1,"id":"3afb71cf_e4b81d2c","line":64,"updated":"2015-06-10 19:45:58.000000000","message":"Very nice that you will keep this backward compatible until end of life of previous API versions","commit_id":"07653211dfc6373768d02d4c79c4c7c1cf91105e"},{"author":{"_account_id":6460,"name":"Brad Topol","email":"btopol@us.ibm.com","username":"btopol"},"change_message_id":"43c161c36b43f952ddcd608f98f66b1ae08dc852","unresolved":false,"context_lines":[{"line_number":68,"context_line":""},{"line_number":69,"context_line":".. note::"},{"line_number":70,"context_line":""},{"line_number":71,"context_line":"    The details on the specific API changes and more in-depth design will need"},{"line_number":72,"context_line":"    to be addressed when this is moved from the backlog to the accepted spec"},{"line_number":73,"context_line":"    location for a release."},{"line_number":74,"context_line":""}],"source_content_type":"text/x-rst","patch_set":1,"id":"3afb71cf_04957985","line":71,"updated":"2015-06-10 19:45:58.000000000","message":"I\u0027m assuming you will do this in a follow-on patch to the API doc, correct","commit_id":"07653211dfc6373768d02d4c79c4c7c1cf91105e"},{"author":{"_account_id":2903,"name":"Morgan Fainberg","email":"morgan.fainberg@gmail.com","username":"mdrnstm"},"change_message_id":"8fb30035a32b560900ce37b05bab955bb57c9643","unresolved":false,"context_lines":[{"line_number":68,"context_line":""},{"line_number":69,"context_line":".. note::"},{"line_number":70,"context_line":""},{"line_number":71,"context_line":"    The details on the specific API changes and more in-depth design will need"},{"line_number":72,"context_line":"    to be addressed when this is moved from the backlog to the accepted spec"},{"line_number":73,"context_line":"    location for a release."},{"line_number":74,"context_line":""}],"source_content_type":"text/x-rst","patch_set":1,"id":"3afb71cf_96806d8c","line":71,"in_reply_to":"3afb71cf_04957985","updated":"2015-06-11 04:43:26.000000000","message":"When you move this from the backlog to targeted, yes.","commit_id":"07653211dfc6373768d02d4c79c4c7c1cf91105e"},{"author":{"_account_id":6460,"name":"Brad Topol","email":"btopol@us.ibm.com","username":"btopol"},"change_message_id":"43c161c36b43f952ddcd608f98f66b1ae08dc852","unresolved":false,"context_lines":[{"line_number":96,"context_line":"Other End User Impact"},{"line_number":97,"context_line":"---------------------"},{"line_number":98,"context_line":""},{"line_number":99,"context_line":"* This will change how authentication works, however the old systems will"},{"line_number":100,"context_line":"  continue to function. With the use of ``keystoneauth`` as a library, the"},{"line_number":101,"context_line":"  change should end up seamless to consumers of the new library."},{"line_number":102,"context_line":""}],"source_content_type":"text/x-rst","patch_set":1,"id":"3afb71cf_244f5538","line":99,"updated":"2015-06-10 19:45:58.000000000","message":"Thanks again for remaining backward compatible  :-)","commit_id":"07653211dfc6373768d02d4c79c4c7c1cf91105e"}]}