)]}'
{"specs/backlog/merge_role_id.rst":[{"author":{"_account_id":1941,"name":"Lin Hua Cheng","email":"os.lcheng@gmail.com","username":"lin-hua-cheng"},"change_message_id":"861419a56eaccb00a1b64665eba1147b4debf525","unresolved":false,"context_lines":[{"line_number":10,"context_line":""},{"line_number":11,"context_line":"`bp example \u003chttps://blueprints.launchpad.net/keystone/+spec/merge-role-id\u003e`_"},{"line_number":12,"context_line":""},{"line_number":13,"context_line":"Merge the role id and role name into a single, human readable field."},{"line_number":14,"context_line":""},{"line_number":15,"context_line":""},{"line_number":16,"context_line":"Problem Description"}],"source_content_type":"text/x-rst","patch_set":2,"id":"ba3cc151_469a4670","line":13,"updated":"2015-07-10 00:26:56.000000000","message":"We\u0027re not merging the id to name, but Replacing id with role name. It might be clearer that way?\n\nMerging makes me think that the new role name will be \u003crole_id\u003e_\u003crole_name\u003e","commit_id":"5e0f43c6f3f69cc017a58811fd56ba21abe008e7"},{"author":{"_account_id":8119,"name":"Eric Brown","email":"eric_wade_brown@yahoo.com","username":"ericwb"},"change_message_id":"1e83e38943e895bda579f0ac4fd90e32b4974026","unresolved":false,"context_lines":[{"line_number":17,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":18,"context_line":""},{"line_number":19,"context_line":"Role IDs are used for assignments.  Role names are used for role based access"},{"line_number":20,"context_line":"control enforcement.  This force the role name to be globally unique.  Thus,"},{"line_number":21,"context_line":"the role_id is a redundant field.  In order to properly parse documents that"},{"line_number":22,"context_line":"have roles in them, we should match the role id to the role name, but this"},{"line_number":23,"context_line":"means that either all documents need to carry both, or that parsers need an"}],"source_content_type":"text/x-rst","patch_set":2,"id":"dac4157f_9ea59948","line":20,"updated":"2015-04-22 16:07:45.000000000","message":"This forces","commit_id":"5e0f43c6f3f69cc017a58811fd56ba21abe008e7"},{"author":{"_account_id":8119,"name":"Eric Brown","email":"eric_wade_brown@yahoo.com","username":"ericwb"},"change_message_id":"6e33c7ee2d77a93cfcb12c516cf7f5375546c778","unresolved":false,"context_lines":[{"line_number":18,"context_line":""},{"line_number":19,"context_line":"Role IDs are used for assignments.  Role names are used for role based access"},{"line_number":20,"context_line":"control enforcement.  This force the role name to be globally unique.  Thus,"},{"line_number":21,"context_line":"the role_id is a redundant field.  In order to properly parse documents that"},{"line_number":22,"context_line":"have roles in them, we should match the role id to the role name, but this"},{"line_number":23,"context_line":"means that either all documents need to carry both, or that parsers need an"},{"line_number":24,"context_line":"outside channel to query the role name to id lookup."}],"source_content_type":"text/x-rst","patch_set":2,"id":"fa32b979_7d155e47","line":21,"updated":"2015-06-26 23:24:27.000000000","message":"Sorry I\u0027m not clear.  What documents are you referring to?","commit_id":"5e0f43c6f3f69cc017a58811fd56ba21abe008e7"},{"author":{"_account_id":8119,"name":"Eric Brown","email":"eric_wade_brown@yahoo.com","username":"ericwb"},"change_message_id":"6e33c7ee2d77a93cfcb12c516cf7f5375546c778","unresolved":false,"context_lines":[{"line_number":22,"context_line":"have roles in them, we should match the role id to the role name, but this"},{"line_number":23,"context_line":"means that either all documents need to carry both, or that parsers need an"},{"line_number":24,"context_line":"outside channel to query the role name to id lookup."},{"line_number":25,"context_line":""},{"line_number":26,"context_line":""},{"line_number":27,"context_line":""},{"line_number":28,"context_line":"Proposed Change"}],"source_content_type":"text/x-rst","patch_set":2,"id":"fa32b979_98fdd00a","line":25,"updated":"2015-06-26 23:24:27.000000000","message":"In most RBAC systems the role name is just a human readable string for the end user and the admin can freely rename the role as they wish without affecting the privileges.  \n\nIn keystone, roles are tightly tied to policy rules based on their name.  I think it would be better to use role IDs, but realize that\u0027s probably a huge effort to change.","commit_id":"5e0f43c6f3f69cc017a58811fd56ba21abe008e7"},{"author":{"_account_id":13997,"name":"SHIGEMATSU Mitsuhiro","email":"shigematsu.mitsuhiro@lab.ntt.co.jp","username":"pshige"},"change_message_id":"b3d816d8f690ef07242a5b369072e050af03db49","unresolved":false,"context_lines":[{"line_number":41,"context_line":"cannot drop role name, as it is used in policy enforcement."},{"line_number":42,"context_line":""},{"line_number":43,"context_line":"We could force the role_id and role name to be present in every document, but"},{"line_number":44,"context_line":"that leads to potential inconsistancies."},{"line_number":45,"context_line":""},{"line_number":46,"context_line":"Security Impact"},{"line_number":47,"context_line":"---------------"}],"source_content_type":"text/x-rst","patch_set":2,"id":"da20952f_ab7934fe","line":44,"updated":"2015-09-03 13:12:00.000000000","message":"s/inconsistancies/inconsistencies/","commit_id":"5e0f43c6f3f69cc017a58811fd56ba21abe008e7"},{"author":{"_account_id":13997,"name":"SHIGEMATSU Mitsuhiro","email":"shigematsu.mitsuhiro@lab.ntt.co.jp","username":"pshige"},"change_message_id":"b3d816d8f690ef07242a5b369072e050af03db49","unresolved":false,"context_lines":[{"line_number":46,"context_line":"Security Impact"},{"line_number":47,"context_line":"---------------"},{"line_number":48,"context_line":""},{"line_number":49,"context_line":"The net effect should be improved security.  When performing a role assignemnt,"},{"line_number":50,"context_line":"users will no longer be translating a human string to a UUID role and back."},{"line_number":51,"context_line":""},{"line_number":52,"context_line":"Policy will be enforced on the same value present in the role assignment."}],"source_content_type":"text/x-rst","patch_set":2,"id":"da20952f_cb634840","line":49,"updated":"2015-09-03 13:12:00.000000000","message":"s/assignemnt/assignment/","commit_id":"5e0f43c6f3f69cc017a58811fd56ba21abe008e7"},{"author":{"_account_id":8119,"name":"Eric Brown","email":"eric_wade_brown@yahoo.com","username":"ericwb"},"change_message_id":"1e83e38943e895bda579f0ac4fd90e32b4974026","unresolved":false,"context_lines":[{"line_number":47,"context_line":"---------------"},{"line_number":48,"context_line":""},{"line_number":49,"context_line":"The net effect should be improved security.  When performing a role assignemnt,"},{"line_number":50,"context_line":"users will no longer be translating a human string to a UUID role and back."},{"line_number":51,"context_line":""},{"line_number":52,"context_line":"Policy will be enforced on the same value present in the role assignment."},{"line_number":53,"context_line":""}],"source_content_type":"text/x-rst","patch_set":2,"id":"dac4157f_d2bc2508","line":50,"updated":"2015-04-22 16:07:45.000000000","message":"Is this really improved security?\n\nAnd I thought both the CLI and Horizon already allow the user to give the role name during a grant.","commit_id":"5e0f43c6f3f69cc017a58811fd56ba21abe008e7"},{"author":{"_account_id":1941,"name":"Lin Hua Cheng","email":"os.lcheng@gmail.com","username":"lin-hua-cheng"},"change_message_id":"861419a56eaccb00a1b64665eba1147b4debf525","unresolved":false,"context_lines":[{"line_number":47,"context_line":"---------------"},{"line_number":48,"context_line":""},{"line_number":49,"context_line":"The net effect should be improved security.  When performing a role assignemnt,"},{"line_number":50,"context_line":"users will no longer be translating a human string to a UUID role and back."},{"line_number":51,"context_line":""},{"line_number":52,"context_line":"Policy will be enforced on the same value present in the role assignment."},{"line_number":53,"context_line":""}],"source_content_type":"text/x-rst","patch_set":2,"id":"ba3cc151_667aea27","line":50,"in_reply_to":"dac4157f_d2bc2508","updated":"2015-07-10 00:26:56.000000000","message":"This is more of usability impact, perhaps move it to the section down?","commit_id":"5e0f43c6f3f69cc017a58811fd56ba21abe008e7"},{"author":{"_account_id":8119,"name":"Eric Brown","email":"eric_wade_brown@yahoo.com","username":"ericwb"},"change_message_id":"1e83e38943e895bda579f0ac4fd90e32b4974026","unresolved":false,"context_lines":[{"line_number":52,"context_line":"Policy will be enforced on the same value present in the role assignment."},{"line_number":53,"context_line":""},{"line_number":54,"context_line":"Role names will still need to be kept as clear as possible.  Changing the"},{"line_number":55,"context_line":"data type useed in assignment will not change that.  Since both id and name"},{"line_number":56,"context_line":"are required to be present in the token according to the V3 spec, both need to"},{"line_number":57,"context_line":"abide by the same rules for strings and unique identifies already."},{"line_number":58,"context_line":""}],"source_content_type":"text/x-rst","patch_set":2,"id":"dac4157f_d21b0572","line":55,"updated":"2015-04-22 16:07:45.000000000","message":"useed -\u003e used","commit_id":"5e0f43c6f3f69cc017a58811fd56ba21abe008e7"},{"author":{"_account_id":8119,"name":"Eric Brown","email":"eric_wade_brown@yahoo.com","username":"ericwb"},"change_message_id":"1e83e38943e895bda579f0ac4fd90e32b4974026","unresolved":false,"context_lines":[{"line_number":54,"context_line":"Role names will still need to be kept as clear as possible.  Changing the"},{"line_number":55,"context_line":"data type useed in assignment will not change that.  Since both id and name"},{"line_number":56,"context_line":"are required to be present in the token according to the V3 spec, both need to"},{"line_number":57,"context_line":"abide by the same rules for strings and unique identifies already."},{"line_number":58,"context_line":""},{"line_number":59,"context_line":""},{"line_number":60,"context_line":"Notifications Impact"}],"source_content_type":"text/x-rst","patch_set":2,"id":"dac4157f_123dfdc3","line":57,"updated":"2015-04-22 16:07:45.000000000","message":"identifies -\u003e identities?","commit_id":"5e0f43c6f3f69cc017a58811fd56ba21abe008e7"},{"author":{"_account_id":1941,"name":"Lin Hua Cheng","email":"os.lcheng@gmail.com","username":"lin-hua-cheng"},"change_message_id":"861419a56eaccb00a1b64665eba1147b4debf525","unresolved":false,"context_lines":[{"line_number":76,"context_line":"Other Deployer Impact"},{"line_number":77,"context_line":"---------------------"},{"line_number":78,"context_line":""},{"line_number":79,"context_line":""},{"line_number":80,"context_line":"No new configuration options are required."},{"line_number":81,"context_line":""},{"line_number":82,"context_line":"The change to exisitng roles will take place after a sql migration.  The"}],"source_content_type":"text/x-rst","patch_set":2,"id":"ba3cc151_461566e3","line":79,"updated":"2015-07-10 00:26:56.000000000","message":"extra space","commit_id":"5e0f43c6f3f69cc017a58811fd56ba21abe008e7"},{"author":{"_account_id":1941,"name":"Lin Hua Cheng","email":"os.lcheng@gmail.com","username":"lin-hua-cheng"},"change_message_id":"861419a56eaccb00a1b64665eba1147b4debf525","unresolved":false,"context_lines":[{"line_number":79,"context_line":""},{"line_number":80,"context_line":"No new configuration options are required."},{"line_number":81,"context_line":""},{"line_number":82,"context_line":"The change to exisitng roles will take place after a sql migration.  The"},{"line_number":83,"context_line":"change to role creation will take place immediately after merge."},{"line_number":84,"context_line":""},{"line_number":85,"context_line":""}],"source_content_type":"text/x-rst","patch_set":2,"id":"ba3cc151_c69bb665","line":82,"updated":"2015-07-10 00:26:56.000000000","message":"exisitng -\u003e existing","commit_id":"5e0f43c6f3f69cc017a58811fd56ba21abe008e7"},{"author":{"_account_id":1941,"name":"Lin Hua Cheng","email":"os.lcheng@gmail.com","username":"lin-hua-cheng"},"change_message_id":"861419a56eaccb00a1b64665eba1147b4debf525","unresolved":false,"context_lines":[{"line_number":106,"context_line":""},{"line_number":107,"context_line":"*  Change role creation code to use role name as role id"},{"line_number":108,"context_line":""},{"line_number":109,"context_line":"*  Migrate existing roles and assignements to use the role name as the role id."},{"line_number":110,"context_line":""},{"line_number":111,"context_line":""},{"line_number":112,"context_line":"Dependencies"}],"source_content_type":"text/x-rst","patch_set":2,"id":"ba3cc151_26ab8277","line":109,"updated":"2015-07-10 00:26:56.000000000","message":"assignements  -\u003e assignments","commit_id":"5e0f43c6f3f69cc017a58811fd56ba21abe008e7"},{"author":{"_account_id":8866,"name":"Raildo Mascena de Sousa Filho","email":"rmascena@redhat.com","username":"raildo"},"change_message_id":"aad9804cd8365bdc4dbe67b9d7eb09608b1d46d2","unresolved":false,"context_lines":[{"line_number":125,"context_line":"References"},{"line_number":126,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":127,"context_line":""},{"line_number":128,"context_line":"Noe additional references cited."}],"source_content_type":"text/x-rst","patch_set":2,"id":"fa32b979_c5bf05a9","line":128,"updated":"2015-06-26 14:21:27.000000000","message":"No","commit_id":"5e0f43c6f3f69cc017a58811fd56ba21abe008e7"}],"specs/next/merge_role_id.rst":[{"author":{"_account_id":13055,"name":"Alexander Makarov","email":"ajiekcahdp.makapob@gmail.com","username":"amakarov"},"change_message_id":"e2539c3fc414465553bfeea12379f8396e4391d9","unresolved":false,"context_lines":[{"line_number":18,"context_line":""},{"line_number":19,"context_line":"Role IDs are used for assignments.  Role names are used for role based access"},{"line_number":20,"context_line":"control enforcement.  This force the role name to be globally unique.  Thus,"},{"line_number":21,"context_line":"the role_id is a redundant field.  In order to properly parse docuemtns that"},{"line_number":22,"context_line":"have roles in them, we should match the role id to the role name, but this"},{"line_number":23,"context_line":"means that either all documents need to carry both, or that parsers need an"},{"line_number":24,"context_line":"outside channel to query the role name to id lookup."}],"source_content_type":"text/x-rst","patch_set":1,"id":"fa81d914_8fb24492","line":21,"range":{"start_line":21,"start_character":62,"end_line":21,"end_character":71},"updated":"2015-01-30 16:18:32.000000000","message":"s/docuemtns/documents/","commit_id":"9b55b2ecc1bde243e55de4442fcc8344f3fef057"},{"author":{"_account_id":220,"name":"Haneef Ali","email":"haneef.ali@hp.com","username":"haneef"},"change_message_id":"f9903584ee0a21d4df88593a810a1f7f839552da","unresolved":false,"context_lines":[{"line_number":34,"context_line":"When creating a role, no longer allow the role_id to be anything other than the"},{"line_number":35,"context_line":"role name."},{"line_number":36,"context_line":""},{"line_number":37,"context_line":"Alternatives"},{"line_number":38,"context_line":"------------"},{"line_number":39,"context_line":""},{"line_number":40,"context_line":"We cannot drop the role_id field, as it is used in many APIs.  We"}],"source_content_type":"text/x-rst","patch_set":1,"id":"da86d52c_6c5db3e9","line":37,"updated":"2015-01-30 20:07:25.000000000","message":"Can you please explain how are you going to migrate?","commit_id":"9b55b2ecc1bde243e55de4442fcc8344f3fef057"}]}
