)]}'
{"api/v3/identity-api-v3.rst":[{"author":{"_account_id":5707,"name":"Henry Nash","email":"henryn@linux.vnet.ibm.com","username":"henry-nash"},"change_message_id":"bb85160e91233342dd76302333e3eb386f683d54","unresolved":false,"context_lines":[{"line_number":12,"context_line":"What\u0027s New in Version 3.4"},{"line_number":13,"context_line":"-------------------------"},{"line_number":14,"context_line":""},{"line_number":15,"context_line":"- Addition of `parent_id` optional attribute to projects. This enables the"},{"line_number":16,"context_line":"  construction of a hierarchy of projects."},{"line_number":17,"context_line":""},{"line_number":18,"context_line":"What\u0027s New in Version 3.3"}],"source_content_type":"text/x-rst","patch_set":1,"id":"5a890539_97f6505c","line":15,"updated":"2014-12-05 20:15:50.000000000","message":"Should add something here about domain-roles being new in 3.4","commit_id":"9f39e96030f6aae7d2ed9d4b2593cf926ea3c81e"},{"author":{"_account_id":5707,"name":"Henry Nash","email":"henryn@linux.vnet.ibm.com","username":"henry-nash"},"change_message_id":"bb85160e91233342dd76302333e3eb386f683d54","unresolved":false,"context_lines":[{"line_number":951,"context_line":"-  ``name`` (string)"},{"line_number":952,"context_line":""},{"line_number":953,"context_line":"Globally unique name of the domain role."},{"line_number":954,"context_line":""},{"line_number":955,"context_line":"-  ``roles`` (list)"},{"line_number":956,"context_line":""},{"line_number":957,"context_line":"Represents the set of ``roles`` whose individual collection of actions are"}],"source_content_type":"text/x-rst","patch_set":1,"id":"5a890539_37867cbb","line":954,"updated":"2014-12-05 20:15:50.000000000","message":"don\u0027t we also need a domain_id ?","commit_id":"9f39e96030f6aae7d2ed9d4b2593cf926ea3c81e"},{"author":{"_account_id":5707,"name":"Henry Nash","email":"henryn@linux.vnet.ibm.com","username":"henry-nash"},"change_message_id":"bb85160e91233342dd76302333e3eb386f683d54","unresolved":false,"context_lines":[{"line_number":953,"context_line":"Globally unique name of the domain role."},{"line_number":954,"context_line":""},{"line_number":955,"context_line":"-  ``roles`` (list)"},{"line_number":956,"context_line":""},{"line_number":957,"context_line":"Represents the set of ``roles`` whose individual collection of actions are"},{"line_number":958,"context_line":"propagated."},{"line_number":959,"context_line":""}],"source_content_type":"text/x-rst","patch_set":1,"id":"5a890539_b760ac0e","line":956,"updated":"2014-12-05 20:15:50.000000000","message":"I\u0027m not sure roles \u0026 domain_roles are attributes.....maybe this is like group membership....you have an API that lists members of the domain_role","commit_id":"9f39e96030f6aae7d2ed9d4b2593cf926ea3c81e"},{"author":{"_account_id":5707,"name":"Henry Nash","email":"henryn@linux.vnet.ibm.com","username":"henry-nash"},"change_message_id":"bb85160e91233342dd76302333e3eb386f683d54","unresolved":false,"context_lines":[{"line_number":4976,"context_line":""},{"line_number":4977,"context_line":"    {"},{"line_number":4978,"context_line":"        \"domain_role\": {"},{"line_number":4979,"context_line":"            \"name\": \"--domain-role-name--\""},{"line_number":4980,"context_line":"        }"},{"line_number":4981,"context_line":"    }"},{"line_number":4982,"context_line":""}],"source_content_type":"text/x-rst","patch_set":1,"id":"5a890539_1747c078","line":4979,"updated":"2014-12-05 20:15:50.000000000","message":"and domain_id....","commit_id":"9f39e96030f6aae7d2ed9d4b2593cf926ea3c81e"},{"author":{"_account_id":5707,"name":"Henry Nash","email":"henryn@linux.vnet.ibm.com","username":"henry-nash"},"change_message_id":"bb85160e91233342dd76302333e3eb386f683d54","unresolved":false,"context_lines":[{"line_number":5099,"context_line":"            \"name\": \"--domain-role-name--\""},{"line_number":5100,"context_line":"        }"},{"line_number":5101,"context_line":"    }"},{"line_number":5102,"context_line":""},{"line_number":5103,"context_line":"Update domain role"},{"line_number":5104,"context_line":"^^^^^^^^^^^^^^^^^^"},{"line_number":5105,"context_line":""}],"source_content_type":"text/x-rst","patch_set":1,"id":"5a890539_da763da3","line":5102,"updated":"2014-12-05 20:15:50.000000000","message":"As indicated earlier, I don\u0027t thick GET /domain_roles/ should include the members like you have above.  I think we have a separate API for that, e.g.:\n\nGET /domain_roles/{domain_role_id}/members\n\nor perhaps\n\nGET /domain_roles/{domain_role_id}/roles\nGET /domain_roles/{domain_role_id}/domain_roles","commit_id":"9f39e96030f6aae7d2ed9d4b2593cf926ea3c81e"},{"author":{"_account_id":1941,"name":"Lin Hua Cheng","email":"os.lcheng@gmail.com","username":"lin-hua-cheng"},"change_message_id":"a1141e25396c09a336920ad7ea6a81f2934f7dcd","unresolved":false,"context_lines":[{"line_number":943,"context_line":"Domain roles are domain specific entities that allow a domain to support its"},{"line_number":944,"context_line":"own set of roles that are meaningful at that domain level."},{"line_number":945,"context_line":"A domain role can map/contain one or more domain roles and/or global roles,"},{"line_number":946,"context_line":"that are referenced in policy files."},{"line_number":947,"context_line":"Domain roles are not included in the role list that is part of a KeyStone"},{"line_number":948,"context_line":"token, rather they are resolved down to their underlying global roles at"},{"line_number":949,"context_line":"token generation time - and it is this set of global roles that will appear."}],"source_content_type":"text/x-rst","patch_set":2,"id":"3a961159_117c9fb4","line":946,"updated":"2014-12-12 00:01:02.000000000","message":"Would the policy file support domain_role name too?","commit_id":"7f79ed82d477a28984d115b83c7288b77ce2b016"},{"author":{"_account_id":5707,"name":"Henry Nash","email":"henryn@linux.vnet.ibm.com","username":"henry-nash"},"change_message_id":"19b8d697a56d82a8dd736db295de293cfedd820c","unresolved":false,"context_lines":[{"line_number":943,"context_line":"Domain roles are domain specific entities that allow a domain to support its"},{"line_number":944,"context_line":"own set of roles that are meaningful at that domain level."},{"line_number":945,"context_line":"A domain role can map/contain one or more domain roles and/or global roles,"},{"line_number":946,"context_line":"that are referenced in policy files."},{"line_number":947,"context_line":"Domain roles are not included in the role list that is part of a KeyStone"},{"line_number":948,"context_line":"token, rather they are resolved down to their underlying global roles at"},{"line_number":949,"context_line":"token generation time - and it is this set of global roles that will appear."}],"source_content_type":"text/x-rst","patch_set":2,"id":"3a961159_92cec32c","line":946,"in_reply_to":"3a961159_117c9fb4","updated":"2014-12-12 10:25:02.000000000","message":"No, domain_roles are always expanded into the list of roles at token creation time, so no change to policy files","commit_id":"7f79ed82d477a28984d115b83c7288b77ce2b016"},{"author":{"_account_id":13478,"name":"Boris Bobrov","email":"b.bobrov@sap.com","username":"bbobrov"},"change_message_id":"002ec91bde82ae8dd9c60e65ccc4cc7ec0f9729e","unresolved":false,"context_lines":[{"line_number":944,"context_line":"own set of roles that are meaningful at that domain level."},{"line_number":945,"context_line":"A domain role can map/contain one or more domain roles and/or global roles,"},{"line_number":946,"context_line":"that are referenced in policy files."},{"line_number":947,"context_line":"Domain roles are not included in the role list that is part of a KeyStone"},{"line_number":948,"context_line":"token, rather they are resolved down to their underlying global roles at"},{"line_number":949,"context_line":"token generation time - and it is this set of global roles that will appear."},{"line_number":950,"context_line":""}],"source_content_type":"text/x-rst","patch_set":2,"id":"3a961159_d15074d6","line":947,"updated":"2014-12-11 09:57:10.000000000","message":"s/KeyStone/Keystone/","commit_id":"7f79ed82d477a28984d115b83c7288b77ce2b016"},{"author":{"_account_id":5707,"name":"Henry Nash","email":"henryn@linux.vnet.ibm.com","username":"henry-nash"},"change_message_id":"93799c913991fe7d6c86e4836479e7b9cfe960f4","unresolved":false,"context_lines":[{"line_number":5163,"context_line":"::"},{"line_number":5164,"context_line":""},{"line_number":5165,"context_line":"    GET /domain_roles/{domain_role_id}/roles"},{"line_number":5166,"context_line":"    GET /domain_roles/{domain_role_id}/domain_roles"},{"line_number":5167,"context_line":""},{"line_number":5168,"context_line":"Relationship:"},{"line_number":5169,"context_line":"``http://docs.openstack.org/api/openstack-identity/3/rel/domain_role_membership``"}],"source_content_type":"text/x-rst","patch_set":2,"id":"3a961159_f5b811e7","line":5166,"updated":"2014-12-10 18:39:59.000000000","message":"so the only thing I don\u0027t like is that you can\u0027t list all the members in one go.  I had thought about having a:\n\nGET /domain_roles/{domain_role_id}/members\n\nwhich would return both sets or roles and domain_roles (but would have to have an embedded structure)....but maybe code that would inspect the results would need to query these differently anyway?","commit_id":"7f79ed82d477a28984d115b83c7288b77ce2b016"},{"author":{"_account_id":9142,"name":"Samuel de Medeiros Queiroz","email":"samueldmq@lsd.ufcg.edu.br","username":"samuel-z","inactive":true},"change_message_id":"45fe9a7b768d8e8c09fb88ed5968752b15bc5227","unresolved":false,"context_lines":[{"line_number":5163,"context_line":"::"},{"line_number":5164,"context_line":""},{"line_number":5165,"context_line":"    GET /domain_roles/{domain_role_id}/roles"},{"line_number":5166,"context_line":"    GET /domain_roles/{domain_role_id}/domain_roles"},{"line_number":5167,"context_line":""},{"line_number":5168,"context_line":"Relationship:"},{"line_number":5169,"context_line":"``http://docs.openstack.org/api/openstack-identity/3/rel/domain_role_membership``"}],"source_content_type":"text/x-rst","patch_set":2,"id":"3a961159_ebf73857","line":5166,"in_reply_to":"3a961159_6eb1a146","updated":"2014-12-11 13:52:01.000000000","message":"With your proposed alternative, that\u0027s in accordance with Boris\u0027  comment, we come to a fair point of discussion here:\n\nAs domain-roles have the same semantic of roles, should they share the same APIs? e.g for granting permissions, we could provide either a role or a domain-role using the same format:\n\n/domains/\u003cdomain_id\u003e/users/\u003cuser_id\u003e/roles/\u003crole_id\u003e\n/domains/\u003cdomain_id\u003e/users/\u003cuser_id\u003e/roles/\u003cdomain_role_id\u003e\n\nSince we have separate tables for them, the impact of this is:\n* When a common operation is requested, e.g granting, we don\u0027t know which table to look in. Having to look at two tables for each operation that involves roles is not the best approach at all.\n\nAlternatives:\ni) Put both entities in a single table. We could do that by adding a \u0027domain_id\u0027 field.\n* Cons:\n** I can\u0027t see a big advantage in querying a single table with size (j + k) instead of querying two tables of size j and k. The advantage would be minimal, as not needing to open two separate sessions, etc;\n** In addition, if we introduce capabilities as a first class citizen of keystone, it would be better to have roles separated from domain-roles, so that: roles -\u003e capabilities and domain-roles -\u003e roles.\n\nii) Create domain-role id that exposes the type of entity it represents. For instance, \u003cdomain-role-id\u003e \u003d \u003cdomain-id\u003e.\u003cdomain-role-id-itself\u003e. This way we can resolve for which table to look in.\n\nAny other option? Pros? Cons?","commit_id":"7f79ed82d477a28984d115b83c7288b77ce2b016"},{"author":{"_account_id":5707,"name":"Henry Nash","email":"henryn@linux.vnet.ibm.com","username":"henry-nash"},"change_message_id":"19b8d697a56d82a8dd736db295de293cfedd820c","unresolved":false,"context_lines":[{"line_number":5163,"context_line":"::"},{"line_number":5164,"context_line":""},{"line_number":5165,"context_line":"    GET /domain_roles/{domain_role_id}/roles"},{"line_number":5166,"context_line":"    GET /domain_roles/{domain_role_id}/domain_roles"},{"line_number":5167,"context_line":""},{"line_number":5168,"context_line":"Relationship:"},{"line_number":5169,"context_line":"``http://docs.openstack.org/api/openstack-identity/3/rel/domain_role_membership``"}],"source_content_type":"text/x-rst","patch_set":2,"id":"3a961159_ed21ec4d","line":5166,"in_reply_to":"3a961159_ebf73857","updated":"2014-12-12 10:25:02.000000000","message":"A sensible set of options.  In alternative i), this would only be for the actually assignment GET/PUT/DELETE - we would still need separate APIs for the management of the domain_roles themselves.  Given that, I\u0027m not sure we gain that much in terms of API reduction by sharing the same assignment API....and I would vote for clarity and keep them separate (as stated in the current spec) - but interested in other people\u0027s views.","commit_id":"7f79ed82d477a28984d115b83c7288b77ce2b016"},{"author":{"_account_id":9142,"name":"Samuel de Medeiros Queiroz","email":"samueldmq@lsd.ufcg.edu.br","username":"samuel-z","inactive":true},"change_message_id":"9bc124f23ee7583b9fe1199667650d560a887e2f","unresolved":false,"context_lines":[{"line_number":5163,"context_line":"::"},{"line_number":5164,"context_line":""},{"line_number":5165,"context_line":"    GET /domain_roles/{domain_role_id}/roles"},{"line_number":5166,"context_line":"    GET /domain_roles/{domain_role_id}/domain_roles"},{"line_number":5167,"context_line":""},{"line_number":5168,"context_line":"Relationship:"},{"line_number":5169,"context_line":"``http://docs.openstack.org/api/openstack-identity/3/rel/domain_role_membership``"}],"source_content_type":"text/x-rst","patch_set":2,"id":"3a961159_55a337b1","line":5166,"in_reply_to":"3a961159_ed21ec4d","updated":"2014-12-23 22:52:38.000000000","message":"Well, I agree with you.\nI am going to create a new version of this API change including the APIs for CRUD role assignments using domain-roles.\n\nAfter this we can get more views on this.","commit_id":"7f79ed82d477a28984d115b83c7288b77ce2b016"},{"author":{"_account_id":5707,"name":"Henry Nash","email":"henryn@linux.vnet.ibm.com","username":"henry-nash"},"change_message_id":"a5bf505fbbb68a58304b03a67122ed17336125aa","unresolved":false,"context_lines":[{"line_number":5163,"context_line":"::"},{"line_number":5164,"context_line":""},{"line_number":5165,"context_line":"    GET /domain_roles/{domain_role_id}/roles"},{"line_number":5166,"context_line":"    GET /domain_roles/{domain_role_id}/domain_roles"},{"line_number":5167,"context_line":""},{"line_number":5168,"context_line":"Relationship:"},{"line_number":5169,"context_line":"``http://docs.openstack.org/api/openstack-identity/3/rel/domain_role_membership``"}],"source_content_type":"text/x-rst","patch_set":2,"id":"3a961159_6eb1a146","line":5166,"in_reply_to":"3a961159_f5b811e7","updated":"2014-12-11 08:29:13.000000000","message":"Just for clarity, I\u0027m suggesting this in addition to the above.  If we WERE to add it (and I\u0027m definitely not entirely convinced myself), the output might be something like:\n\n\"members\": {\n    domain_roles\": [\n            {\n                \"id\": \"--domain-role-id--\",\n                \"links\": {\n                    \"self\": \"http://identity:35357/v3/roles/--domain-role-id--\"\n                 },\n                \"name\": \"--domain-role-name--\"\n            },\n            {\n                \"id\": \"--domain-role-id--\",\n                \"links\": {\n                    \"self\": \"http://identity:35357/v3/roles/--domain-role-id--\"\n                 },\n                \"name\": \"--domain-role-name--\"\n            }\n        ],\n    roles\": [\n            {\n                \"id\": \"--role-id--\",\n                \"links\": {\n                    \"self\": \"http://identity:35357/v3/roles/--role-id--\"\n                 },\n                \"name\": \"--role-name--\"\n            },\n            {\n                \"id\": \"--ole-id--\",\n                \"links\": {\n                    \"self\": \"http://identity:35357/v3/roles/--role-id--\"\n                 },\n                \"name\": \"--role-name--\"\n            }\n        ],\n    }\n\"links\":\n    \"self\": \"self\": \"http://identity:35357/v3/domain_roles/--domain-role-id--/members\",\n    \"previous\": null,\n    \"next\": null\n}","commit_id":"7f79ed82d477a28984d115b83c7288b77ce2b016"},{"author":{"_account_id":1916,"name":"Guang Yee","email":"gyee@suse.com","username":"guang-yee"},"change_message_id":"0a2140e8d0ba73ee8085f09f9fe14ea262277f80","unresolved":false,"context_lines":[{"line_number":937,"context_line":"        }"},{"line_number":938,"context_line":"    }"},{"line_number":939,"context_line":""},{"line_number":940,"context_line":"Domain Roles: ``/v3/domain_roles/``"},{"line_number":941,"context_line":"~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~"},{"line_number":942,"context_line":""},{"line_number":943,"context_line":"Domain roles are domain specific entities that allow a domain to support its"}],"source_content_type":"text/x-rst","patch_set":3,"id":"3a961159_9b94d78d","line":940,"updated":"2014-12-15 19:07:28.000000000","message":"I don\u0027t understand why it is necessary to create a new resource for domain-owned roles. It should be an attribute of the existing role definition. For example, add \u0027domain_id\u0027 to the existing role definition. If \u0027domain_id\u0027 is None or \u0027default\u0027, then it is a global role definition.\n\nThis is the same argument for merging projects with domains. Lets keep the paradigm consistent.","commit_id":"2f914df6cbbc30b7cedab7e4870a053e24608a52"},{"author":{"_account_id":9142,"name":"Samuel de Medeiros Queiroz","email":"samueldmq@lsd.ufcg.edu.br","username":"samuel-z","inactive":true},"change_message_id":"8a740edbf99f360b352b5d8cf9e4ae1ab85e166e","unresolved":false,"context_lines":[{"line_number":937,"context_line":"        }"},{"line_number":938,"context_line":"    }"},{"line_number":939,"context_line":""},{"line_number":940,"context_line":"Domain Roles: ``/v3/domain_roles/``"},{"line_number":941,"context_line":"~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~"},{"line_number":942,"context_line":""},{"line_number":943,"context_line":"Domain roles are domain specific entities that allow a domain to support its"}],"source_content_type":"text/x-rst","patch_set":3,"id":"3a961159_552ed743","line":940,"in_reply_to":"3a961159_52cef75a","updated":"2014-12-23 22:52:24.000000000","message":"Well, I agree with Henry.\nRoles will really be service capabilities (owned by the service) and domain-roles will be the real roles (group of capabilities, used by domain-admins), in the future.\n\nHaving this as argument implies in having separate backends as a better choice.","commit_id":"2f914df6cbbc30b7cedab7e4870a053e24608a52"},{"author":{"_account_id":1916,"name":"Guang Yee","email":"gyee@suse.com","username":"guang-yee"},"change_message_id":"73cd8231c1bbf8df0fa7d6792f71e6489ea568f3","unresolved":false,"context_lines":[{"line_number":937,"context_line":"        }"},{"line_number":938,"context_line":"    }"},{"line_number":939,"context_line":""},{"line_number":940,"context_line":"Domain Roles: ``/v3/domain_roles/``"},{"line_number":941,"context_line":"~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~"},{"line_number":942,"context_line":""},{"line_number":943,"context_line":"Domain roles are domain specific entities that allow a domain to support its"}],"source_content_type":"text/x-rst","patch_set":3,"id":"3a961159_af2291a0","line":940,"in_reply_to":"3a961159_8781d5fd","updated":"2014-12-19 21:46:30.000000000","message":"Well that\u0027s weird. So are we saying \u0027admin\u0027 is just service capability? I would think the API itself (i.e. identity:list_user) is a service capability, and a role is a collection of service capabilities. Anything more than that are just unnecessary complexity.","commit_id":"2f914df6cbbc30b7cedab7e4870a053e24608a52"},{"author":{"_account_id":5707,"name":"Henry Nash","email":"henryn@linux.vnet.ibm.com","username":"henry-nash"},"change_message_id":"19888330e7ba6a26fdfe185eddc78d7984658c90","unresolved":false,"context_lines":[{"line_number":937,"context_line":"        }"},{"line_number":938,"context_line":"    }"},{"line_number":939,"context_line":""},{"line_number":940,"context_line":"Domain Roles: ``/v3/domain_roles/``"},{"line_number":941,"context_line":"~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~"},{"line_number":942,"context_line":""},{"line_number":943,"context_line":"Domain roles are domain specific entities that allow a domain to support its"}],"source_content_type":"text/x-rst","patch_set":3,"id":"3a961159_8781d5fd","line":940,"in_reply_to":"3a961159_9b94d78d","updated":"2014-12-15 23:17:41.000000000","message":"So I disagree.  I don\u0027t think the project/domain argument has any relevance here.  Roles and Domain_roles are totally different animals - owned and managed by very different people.  What we call a role today is really a service capability and should (really) be owned by the service - maybe even registered on startup.  Domain_roles are the thing we will come to treat as \"the real roles\" in the future.  Combining them makes this divergence more difficult.","commit_id":"2f914df6cbbc30b7cedab7e4870a053e24608a52"},{"author":{"_account_id":5707,"name":"Henry Nash","email":"henryn@linux.vnet.ibm.com","username":"henry-nash"},"change_message_id":"5c97ce3b166550a282447cbc248762658f750d0a","unresolved":false,"context_lines":[{"line_number":937,"context_line":"        }"},{"line_number":938,"context_line":"    }"},{"line_number":939,"context_line":""},{"line_number":940,"context_line":"Domain Roles: ``/v3/domain_roles/``"},{"line_number":941,"context_line":"~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~"},{"line_number":942,"context_line":""},{"line_number":943,"context_line":"Domain roles are domain specific entities that allow a domain to support its"}],"source_content_type":"text/x-rst","patch_set":3,"id":"3a961159_52cef75a","line":940,"in_reply_to":"3a961159_af2291a0","updated":"2014-12-23 16:22:55.000000000","message":"So I think the existing roles will indeed trend towards being just the APIs, with a few \"special shorthands\" (like admin) defined by the service owner. The more general grouping of these roles for use by users in a domain will use domain-roles, which allow them  to create their own, meaningful (only to them) abstraction.","commit_id":"2f914df6cbbc30b7cedab7e4870a053e24608a52"},{"author":{"_account_id":13055,"name":"Alexander Makarov","email":"ajiekcahdp.makapob@gmail.com","username":"amakarov"},"change_message_id":"df3f5c7341667f5b9cdece4f8d44fbd065e38739","unresolved":false,"context_lines":[{"line_number":958,"context_line":""},{"line_number":959,"context_line":"References the domain which owns the domain role; if a domain is not specified"},{"line_number":960,"context_line":"by the client, the Identity service implementation will default it to"},{"line_number":961,"context_line":"the domain to which the client\u0027s token is scoped."},{"line_number":962,"context_line":""},{"line_number":963,"context_line":"Example entity:"},{"line_number":964,"context_line":""}],"source_content_type":"text/x-rst","patch_set":3,"id":"3a961159_917045a5","line":961,"updated":"2014-12-15 13:38:40.000000000","message":"So domainA-scoped token can create a role for domainB? I presume, there must be some constraints and rules - are they specified somewhere?","commit_id":"2f914df6cbbc30b7cedab7e4870a053e24608a52"},{"author":{"_account_id":9142,"name":"Samuel de Medeiros Queiroz","email":"samueldmq@lsd.ufcg.edu.br","username":"samuel-z","inactive":true},"change_message_id":"8a740edbf99f360b352b5d8cf9e4ae1ab85e166e","unresolved":false,"context_lines":[{"line_number":958,"context_line":""},{"line_number":959,"context_line":"References the domain which owns the domain role; if a domain is not specified"},{"line_number":960,"context_line":"by the client, the Identity service implementation will default it to"},{"line_number":961,"context_line":"the domain to which the client\u0027s token is scoped."},{"line_number":962,"context_line":""},{"line_number":963,"context_line":"Example entity:"},{"line_number":964,"context_line":""}],"source_content_type":"text/x-rst","patch_set":3,"id":"3a961159_35130b02","line":961,"in_reply_to":"3a961159_8798f56b","updated":"2014-12-23 22:52:24.000000000","message":"Agreed!","commit_id":"2f914df6cbbc30b7cedab7e4870a053e24608a52"},{"author":{"_account_id":5707,"name":"Henry Nash","email":"henryn@linux.vnet.ibm.com","username":"henry-nash"},"change_message_id":"19888330e7ba6a26fdfe185eddc78d7984658c90","unresolved":false,"context_lines":[{"line_number":958,"context_line":""},{"line_number":959,"context_line":"References the domain which owns the domain role; if a domain is not specified"},{"line_number":960,"context_line":"by the client, the Identity service implementation will default it to"},{"line_number":961,"context_line":"the domain to which the client\u0027s token is scoped."},{"line_number":962,"context_line":""},{"line_number":963,"context_line":"Example entity:"},{"line_number":964,"context_line":""}],"source_content_type":"text/x-rst","patch_set":3,"id":"3a961159_8798f56b","line":961,"in_reply_to":"3a961159_917045a5","updated":"2014-12-15 23:17:41.000000000","message":"That would depend on the keystone policy file.  You cold create a policy that meant you could only create domain_roles for the same domain as you  have a scoped token (I would think that would be the default), but other polices would be possible.","commit_id":"2f914df6cbbc30b7cedab7e4870a053e24608a52"},{"author":{"_account_id":9142,"name":"Samuel de Medeiros Queiroz","email":"samueldmq@lsd.ufcg.edu.br","username":"samuel-z","inactive":true},"change_message_id":"54013c15c70d6c2844b82dd78b69ef24107c0ff5","unresolved":false,"context_lines":[{"line_number":4799,"context_line":""},{"line_number":4800,"context_line":"Optional query parameters:"},{"line_number":4801,"context_line":""},{"line_number":4802,"context_line":"-  ``group.id`` (string)"},{"line_number":4803,"context_line":"-  ``role.id`` (string)"},{"line_number":4804,"context_line":"-  ``scope.domain.id`` (string)"},{"line_number":4805,"context_line":"-  ``scope.project.id`` (string)"}],"source_content_type":"text/x-rst","patch_set":4,"id":"3a961159_9363f7af","line":4802,"updated":"2014-12-24 00:48:35.000000000","message":"Should we add domain_role.id filter here?\n\nAlso, I think we need to update effective documentation in order to make it clear that domain-roles will be expanded to global roles if effective option is used.","commit_id":"bec7f1fe10eb3dc7372868818bb81de50ec6cc05"},{"author":{"_account_id":9142,"name":"Samuel de Medeiros Queiroz","email":"samueldmq@lsd.ufcg.edu.br","username":"samuel-z","inactive":true},"change_message_id":"54013c15c70d6c2844b82dd78b69ef24107c0ff5","unresolved":false,"context_lines":[{"line_number":5231,"context_line":""},{"line_number":5232,"context_line":"    Status: 204 No Content"},{"line_number":5233,"context_line":""},{"line_number":5234,"context_line":"Grant domain role to user on domain"},{"line_number":5235,"context_line":"^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^"},{"line_number":5236,"context_line":""},{"line_number":5237,"context_line":"::"}],"source_content_type":"text/x-rst","patch_set":4,"id":"3a961159_33bc0306","line":5234,"updated":"2014-12-24 00:48:35.000000000","message":"Introducing separate APIs to assign roles/domain-roles adds 16 new APIs.\n\nSee lines 5234-5593","commit_id":"bec7f1fe10eb3dc7372868818bb81de50ec6cc05"},{"author":{"_account_id":220,"name":"Haneef Ali","email":"haneef.ali@hp.com","username":"haneef"},"change_message_id":"d06538023c47c48694fa1180e528ab265c18dc9b","unresolved":false,"context_lines":[{"line_number":918,"context_line":"                \"self\": \"http://identity:35357/v3/roles/76e72a\""},{"line_number":919,"context_line":"            },"},{"line_number":920,"context_line":"            \"name\": \"admin\""},{"line_number":921,"context_line":"        }"},{"line_number":922,"context_line":"    }"},{"line_number":923,"context_line":""},{"line_number":924,"context_line":"Domain Roles: ``/v3/domain_roles/``"}],"source_content_type":"text/x-rst","patch_set":5,"id":"1a930d6b_9f97a839","line":921,"updated":"2015-01-26 21:19:11.000000000","message":"May be I have missed the conversation. Is domain_roles inheritable?","commit_id":"d40afc13f5565c6831231fb15496a4af2516ec47"},{"author":{"_account_id":9142,"name":"Samuel de Medeiros Queiroz","email":"samueldmq@lsd.ufcg.edu.br","username":"samuel-z","inactive":true},"change_message_id":"e744c71376bd42eafcc5ae378e04eaee19047e36","unresolved":false,"context_lines":[{"line_number":918,"context_line":"                \"self\": \"http://identity:35357/v3/roles/76e72a\""},{"line_number":919,"context_line":"            },"},{"line_number":920,"context_line":"            \"name\": \"admin\""},{"line_number":921,"context_line":"        }"},{"line_number":922,"context_line":"    }"},{"line_number":923,"context_line":""},{"line_number":924,"context_line":"Domain Roles: ``/v3/domain_roles/``"}],"source_content_type":"text/x-rst","patch_set":5,"id":"1a930d6b_1c381cee","line":921,"in_reply_to":"1a930d6b_9f97a839","updated":"2015-01-27 02:17:35.000000000","message":"Yes, they can be inherited.\n\nThere is a spec [1] that proposes domain-roles themselves, here we are agreeing on API change. You may go there for further information in the concept.\n\n[1] https://review.openstack.org/#/c/133855/","commit_id":"d40afc13f5565c6831231fb15496a4af2516ec47"}]}
