)]}'
{"specs/mitaka/ldap-rbac.rst":[{"author":{"_account_id":8119,"name":"Eric Brown","email":"eric_wade_brown@yahoo.com","username":"ericwb"},"change_message_id":"dc228ab75ce31275280e619517e213f9ba9c499a","unresolved":false,"context_lines":[{"line_number":6,"context_line":""},{"line_number":7,"context_line":"The end goal of this initiative is to support Role Based Access Control"},{"line_number":8,"context_line":"with LDAP as backend."},{"line_number":9,"context_line":"This solution based on idea that user already has configured permissions"},{"line_number":10,"context_line":"for users and this configuration is stored in OpenLDAP or Active Directory."},{"line_number":11,"context_line":"The oslo.policy should be able to read permissions not only from policy.json"},{"line_number":12,"context_line":"file but also from OpenLDAP/AD."},{"line_number":13,"context_line":""}],"source_content_type":"text/x-rst","patch_set":1,"id":"da6ed579_dc2fbff4","line":10,"range":{"start_line":9,"start_character":33,"end_line":10,"end_character":74},"updated":"2016-01-18 07:40:43.000000000","message":"Are there deployers that actually do this?  I would be very surprised since permissions are application specific and not well suited in centralized applications such as LDAP.  I don\u0027t think I\u0027ve ever seen a product successfully use LDAP for RBAC.","commit_id":"499946d883ff4d026e347f4a873eb9575d081e9b"},{"author":{"_account_id":8119,"name":"Eric Brown","email":"eric_wade_brown@yahoo.com","username":"ericwb"},"change_message_id":"dc228ab75ce31275280e619517e213f9ba9c499a","unresolved":false,"context_lines":[{"line_number":8,"context_line":"with LDAP as backend."},{"line_number":9,"context_line":"This solution based on idea that user already has configured permissions"},{"line_number":10,"context_line":"for users and this configuration is stored in OpenLDAP or Active Directory."},{"line_number":11,"context_line":"The oslo.policy should be able to read permissions not only from policy.json"},{"line_number":12,"context_line":"file but also from OpenLDAP/AD."},{"line_number":13,"context_line":""},{"line_number":14,"context_line":"Problem description"},{"line_number":15,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"}],"source_content_type":"text/x-rst","patch_set":1,"id":"da6ed579_dc16dfa6","line":12,"range":{"start_line":11,"start_character":34,"end_line":12,"end_character":31},"updated":"2016-01-18 07:40:43.000000000","message":"I would assume performance would suck.","commit_id":"499946d883ff4d026e347f4a873eb9575d081e9b"},{"author":{"_account_id":17860,"name":"Samuel de Medeiros Queiroz","email":"samueldmq@gmail.com","username":"samueldmq"},"change_message_id":"377acde0c51437d6910931f481841fe45f499fa6","unresolved":false,"context_lines":[{"line_number":38,"context_line":""},{"line_number":39,"context_line":"Roles"},{"line_number":40,"context_line":"    -\u003e admin"},{"line_number":41,"context_line":"        Performers: test_user"},{"line_number":42,"context_line":""},{"line_number":43,"context_line":"Permissions"},{"line_number":44,"context_line":"    -\u003e rbacObjectNm\u003didentity"}],"source_content_type":"text/x-rst","patch_set":1,"id":"3a7e1126_02683eb8","line":41,"updated":"2015-12-18 13:06:06.000000000","message":"So in order to this make sense, we also need Role LDAP support, which has been just deprecated in keystone:\n\nhttps://github.com/openstack/keystone/blob/22ab08f/keystone/assignment/role_backends/ldap.py#L32-L35","commit_id":"499946d883ff4d026e347f4a873eb9575d081e9b"},{"author":{"_account_id":5046,"name":"Lance Bragstad","email":"lbragstad@redhat.com","username":"ldbragst"},"change_message_id":"ec9425240b47247d44fa785676629c7abe766cfc","unresolved":false,"context_lines":[{"line_number":38,"context_line":""},{"line_number":39,"context_line":"Roles"},{"line_number":40,"context_line":"    -\u003e admin"},{"line_number":41,"context_line":"        Performers: test_user"},{"line_number":42,"context_line":""},{"line_number":43,"context_line":"Permissions"},{"line_number":44,"context_line":"    -\u003e rbacObjectNm\u003didentity"}],"source_content_type":"text/x-rst","patch_set":1,"id":"9abb7d3a_41a7a7bc","line":41,"in_reply_to":"1a7b0d38_d817e5eb","updated":"2016-06-01 16:26:11.000000000","message":"It sounds like you want a user to get some set of keystone roles based on what roles they have in ldap/ad. This sounds like a mapping engine problem. Dolph is working on a spec to address something like this.","commit_id":"499946d883ff4d026e347f4a873eb9575d081e9b"},{"author":{"_account_id":17862,"name":"Kseniya Tychkova","email":"kseniya.tychkova@gmail.com","username":"ktychkova"},"change_message_id":"296c9b3689ea5d9bba5c10cd223da78a1e23cf88","unresolved":false,"context_lines":[{"line_number":38,"context_line":""},{"line_number":39,"context_line":"Roles"},{"line_number":40,"context_line":"    -\u003e admin"},{"line_number":41,"context_line":"        Performers: test_user"},{"line_number":42,"context_line":""},{"line_number":43,"context_line":"Permissions"},{"line_number":44,"context_line":"    -\u003e rbacObjectNm\u003didentity"}],"source_content_type":"text/x-rst","patch_set":1,"id":"1a7b0d38_d817e5eb","line":41,"in_reply_to":"3a7e1126_02683eb8","updated":"2015-12-23 09:21:13.000000000","message":"This solution doesn\u0027t use keystone API.\nThe main idea is: let\u0027s assume that user already has some RBAC in OpenLDAP and it is not related to Keystone at all.\nThink about this LDAP tree as a set of rules and permissions.","commit_id":"499946d883ff4d026e347f4a873eb9575d081e9b"},{"author":{"_account_id":17860,"name":"Samuel de Medeiros Queiroz","email":"samueldmq@gmail.com","username":"samueldmq"},"change_message_id":"377acde0c51437d6910931f481841fe45f499fa6","unresolved":false,"context_lines":[{"line_number":43,"context_line":"Permissions"},{"line_number":44,"context_line":"    -\u003e rbacObjectNm\u003didentity"},{"line_number":45,"context_line":"        -\u003e rbacOperationNm\u003dlist_users"},{"line_number":46,"context_line":"            rbacRls: admin"},{"line_number":47,"context_line":""},{"line_number":48,"context_line":"**Simple example of schema in OpenLDAP:**"},{"line_number":49,"context_line":""}],"source_content_type":"text/x-rst","patch_set":1,"id":"3a7e1126_82a2eefb","line":46,"updated":"2015-12-18 13:06:06.000000000","message":"Our current \"RBAC rules\" does more than RBAC itself, i.e we also check for scope match. For example, if the project matches with project:%(project_id)s\n\nHow are we going to do this with this structure? Or are we loosing that in favor of this pure RBAC implementaion (which may be a good thing) ?","commit_id":"499946d883ff4d026e347f4a873eb9575d081e9b"},{"author":{"_account_id":17862,"name":"Kseniya Tychkova","email":"kseniya.tychkova@gmail.com","username":"ktychkova"},"change_message_id":"296c9b3689ea5d9bba5c10cd223da78a1e23cf88","unresolved":false,"context_lines":[{"line_number":43,"context_line":"Permissions"},{"line_number":44,"context_line":"    -\u003e rbacObjectNm\u003didentity"},{"line_number":45,"context_line":"        -\u003e rbacOperationNm\u003dlist_users"},{"line_number":46,"context_line":"            rbacRls: admin"},{"line_number":47,"context_line":""},{"line_number":48,"context_line":"**Simple example of schema in OpenLDAP:**"},{"line_number":49,"context_line":""}],"source_content_type":"text/x-rst","patch_set":1,"id":"1a7b0d38_f8cae14e","line":46,"in_reply_to":"3a7e1126_82a2eefb","updated":"2015-12-23 09:21:13.000000000","message":"First of all, we are not going to lose something. This solution adds new backend, old backend still exists. And user will choose backend he wants to use.\nI think it is possible to implement such rules by LDAP, but it is not necessary to do right now.","commit_id":"499946d883ff4d026e347f4a873eb9575d081e9b"},{"author":{"_account_id":17860,"name":"Samuel de Medeiros Queiroz","email":"samueldmq@gmail.com","username":"samueldmq"},"change_message_id":"377acde0c51437d6910931f481841fe45f499fa6","unresolved":false,"context_lines":[{"line_number":90,"context_line":"|            | rbacPermissionNm: identity.list_users                  |"},{"line_number":91,"context_line":"+------------+--------------------------------------------------------+"},{"line_number":92,"context_line":"|            | rbacRls: admin                                         |"},{"line_number":93,"context_line":"+------------+--------------------------------------------------------+"},{"line_number":94,"context_line":""},{"line_number":95,"context_line":"**Steps to check user permission:**"},{"line_number":96,"context_line":""}],"source_content_type":"text/x-rst","patch_set":1,"id":"3a7e1126_02afdee2","line":93,"updated":"2015-12-18 13:06:06.000000000","message":"How do we sync with services adding/removing/updating APIs every release ?\n\nWhat happens in the case a rule doesn\u0027t exist in LDAP but it does in policy.json ?\n\nAlso, are the existing policies (shipped with the code) uploaded to LDAP somehow ?","commit_id":"499946d883ff4d026e347f4a873eb9575d081e9b"},{"author":{"_account_id":17862,"name":"Kseniya Tychkova","email":"kseniya.tychkova@gmail.com","username":"ktychkova"},"change_message_id":"296c9b3689ea5d9bba5c10cd223da78a1e23cf88","unresolved":false,"context_lines":[{"line_number":90,"context_line":"|            | rbacPermissionNm: identity.list_users                  |"},{"line_number":91,"context_line":"+------------+--------------------------------------------------------+"},{"line_number":92,"context_line":"|            | rbacRls: admin                                         |"},{"line_number":93,"context_line":"+------------+--------------------------------------------------------+"},{"line_number":94,"context_line":""},{"line_number":95,"context_line":"**Steps to check user permission:**"},{"line_number":96,"context_line":""}],"source_content_type":"text/x-rst","patch_set":1,"id":"1a7b0d38_78bcb16c","line":93,"in_reply_to":"3a7e1126_02afdee2","updated":"2015-12-23 09:21:13.000000000","message":"Samuel, user will have 2 backends: one uses policy.json other uses OpenLDAP as source for rules. No synchronization between policy.json and OpenLDAP - it is 2 different cases.\nUser can manage rules directly by LDAP or use something like Apache Fortress web interface.\nHow to load existing policies from policy.json file to OpenLDAP - it is good to think about it, but I think it is out of scope. Main idea - user already has rules in OpenLDAP and wants to use them and do not write them in policy.json file.","commit_id":"499946d883ff4d026e347f4a873eb9575d081e9b"},{"author":{"_account_id":17860,"name":"Samuel de Medeiros Queiroz","email":"samueldmq@gmail.com","username":"samueldmq"},"change_message_id":"377acde0c51437d6910931f481841fe45f499fa6","unresolved":false,"context_lines":[{"line_number":146,"context_line":"the same with previously described structure."},{"line_number":147,"context_line":"It means that this solution work with Apache Fortress."},{"line_number":148,"context_line":"All that should be done - properly set parameters in config file."},{"line_number":149,"context_line":""},{"line_number":150,"context_line":"Drawbacks"},{"line_number":151,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":152,"context_line":""}],"source_content_type":"text/x-rst","patch_set":1,"id":"3a7e1126_427f2666","line":149,"updated":"2015-12-18 13:06:06.000000000","message":"We probably want to have a performance section talking about LDAP queries (which may be slow?) affecting all the performance of an OpenStack cloud, as authz checks happen all the time.","commit_id":"499946d883ff4d026e347f4a873eb9575d081e9b"},{"author":{"_account_id":17862,"name":"Kseniya Tychkova","email":"kseniya.tychkova@gmail.com","username":"ktychkova"},"change_message_id":"296c9b3689ea5d9bba5c10cd223da78a1e23cf88","unresolved":false,"context_lines":[{"line_number":146,"context_line":"the same with previously described structure."},{"line_number":147,"context_line":"It means that this solution work with Apache Fortress."},{"line_number":148,"context_line":"All that should be done - properly set parameters in config file."},{"line_number":149,"context_line":""},{"line_number":150,"context_line":"Drawbacks"},{"line_number":151,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":152,"context_line":""}],"source_content_type":"text/x-rst","patch_set":1,"id":"1a7b0d38_18756dca","line":149,"in_reply_to":"3a7e1126_427f2666","updated":"2015-12-23 09:21:13.000000000","message":"It is good point. There is \"Test performance\" item in work items section. I\u0027m sure - we have to do such tests.","commit_id":"499946d883ff4d026e347f4a873eb9575d081e9b"},{"author":{"_account_id":4992,"name":"malini-k-bhandaru","email":"malini.k.bhandaru@intel.com","username":"malini-k-bhandaru"},"change_message_id":"2bc67b701daf6f474c3c79586371961402960abf","unresolved":false,"context_lines":[{"line_number":149,"context_line":""},{"line_number":150,"context_line":"Drawbacks"},{"line_number":151,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":152,"context_line":""},{"line_number":153,"context_line":"This solution adds new functional to oslo.policy and doesn\u0027t make any"},{"line_number":154,"context_line":"changes in old functional."},{"line_number":155,"context_line":"Changes should not affect any components except oslo.policy."}],"source_content_type":"text/x-rst","patch_set":1,"id":"fa69d971_5dc849a8","line":152,"updated":"2016-01-05 10:53:24.000000000","message":"Cannot be called a drawback! Leaves old working stuff as is.\n\nFor performance reasons, when a user authenticates themselves, may be all roles associated with them can be cached. So at least only object access needs only to be checked?","commit_id":"499946d883ff4d026e347f4a873eb9575d081e9b"},{"author":{"_account_id":17862,"name":"Kseniya Tychkova","email":"kseniya.tychkova@gmail.com","username":"ktychkova"},"change_message_id":"9ccb82f413a8e85f62636a21abdf14d9550578f4","unresolved":false,"context_lines":[{"line_number":149,"context_line":""},{"line_number":150,"context_line":"Drawbacks"},{"line_number":151,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":152,"context_line":""},{"line_number":153,"context_line":"This solution adds new functional to oslo.policy and doesn\u0027t make any"},{"line_number":154,"context_line":"changes in old functional."},{"line_number":155,"context_line":"Changes should not affect any components except oslo.policy."}],"source_content_type":"text/x-rst","patch_set":1,"id":"da6ed579_fa2ae72b","line":152,"in_reply_to":"fa69d971_5dc849a8","updated":"2016-01-12 08:04:41.000000000","message":"To cache some information is a good point. I think it is good idea - to test performance and then think what information can be cached.","commit_id":"499946d883ff4d026e347f4a873eb9575d081e9b"},{"author":{"_account_id":4992,"name":"malini-k-bhandaru","email":"malini.k.bhandaru@intel.com","username":"malini-k-bhandaru"},"change_message_id":"2bc67b701daf6f474c3c79586371961402960abf","unresolved":false,"context_lines":[{"line_number":153,"context_line":"This solution adds new functional to oslo.policy and doesn\u0027t make any"},{"line_number":154,"context_line":"changes in old functional."},{"line_number":155,"context_line":"Changes should not affect any components except oslo.policy."},{"line_number":156,"context_line":"oslo.policy should continue work with policy.json without any changes."},{"line_number":157,"context_line":""},{"line_number":158,"context_line":"Alternatives"},{"line_number":159,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"}],"source_content_type":"text/x-rst","patch_set":1,"id":"fa69d971_3d4b152c","line":156,"updated":"2016-01-05 10:53:24.000000000","message":"May want to change these references to oslo.policy to reflect the move to keystone policies.","commit_id":"499946d883ff4d026e347f4a873eb9575d081e9b"}]}
