)]}'
{"specs/keystone/ocata/support-federated-attr.rst":[{"author":{"_account_id":17860,"name":"Samuel de Medeiros Queiroz","email":"samueldmq@gmail.com","username":"samueldmq"},"change_message_id":"e8035958fc6c9e5ece22cfca36db0111988d18f3","unresolved":false,"context_lines":[{"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\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":8,"context_line":"Extend user API to support federated attributes"},{"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\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":10,"context_line":""},{"line_number":11,"context_line":"Extend the user API to support federated attributes in order for operators to"},{"line_number":12,"context_line":"provision authorization."},{"line_number":13,"context_line":""}],"source_content_type":"text/x-rst","patch_set":7,"id":"7a77a97e_d84db49a","line":10,"updated":"2016-11-16 13:25:39.000000000","message":"Please add link to and create a blueprint in launchpad:\n\nBlueprint `support-federated-attr \u003chttps://blueprints.launchpad.net/keystone/+spec/support-federated-attr\u003e`_","commit_id":"b9d0c072002e80dfd3f82c1e3c8710673fd85fe2"},{"author":{"_account_id":18338,"name":"Ron De Rose","email":"ronald.de.rose@intel.com","username":"derosenet"},"change_message_id":"86e35605075553c5b1bcba65012f5581959ccce2","unresolved":false,"context_lines":[{"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\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":8,"context_line":"Extend user API to support federated attributes"},{"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\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":10,"context_line":""},{"line_number":11,"context_line":"Extend the user API to support federated attributes in order for operators to"},{"line_number":12,"context_line":"provision authorization."},{"line_number":13,"context_line":""}],"source_content_type":"text/x-rst","patch_set":7,"id":"7a77a97e_09099631","line":10,"in_reply_to":"7a77a97e_d84db49a","updated":"2016-11-16 16:03:06.000000000","message":"Done","commit_id":"b9d0c072002e80dfd3f82c1e3c8710673fd85fe2"},{"author":{"_account_id":17860,"name":"Samuel de Medeiros Queiroz","email":"samueldmq@gmail.com","username":"samueldmq"},"change_message_id":"8d043bb891d0ca7d8ab024d1b662ecc85ebb5479","unresolved":false,"context_lines":[{"line_number":36,"context_line":""},{"line_number":37,"context_line":"Proposed Change"},{"line_number":38,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":39,"context_line":""},{"line_number":40,"context_line":"We could extend the user API to support federated attributes. So for example,"},{"line_number":41,"context_line":"creating a federated user:"},{"line_number":42,"context_line":""}],"source_content_type":"text/x-rst","patch_set":7,"id":"7a77a97e_5850c45e","line":39,"updated":"2016-11-16 13:24:04.000000000","message":"If I\u0027ve got this spec correctly, this is an enhancement to the shadow mapping proposal. In order to avoid creating entities, etc this would use an API to register and retrieve the federated users so that you can create the delegations (assignments/trusts) explicitly.\n\nIs this correct? If so, we could make this idea clearer.","commit_id":"b9d0c072002e80dfd3f82c1e3c8710673fd85fe2"},{"author":{"_account_id":18338,"name":"Ron De Rose","email":"ronald.de.rose@intel.com","username":"derosenet"},"change_message_id":"86e35605075553c5b1bcba65012f5581959ccce2","unresolved":false,"context_lines":[{"line_number":36,"context_line":""},{"line_number":37,"context_line":"Proposed Change"},{"line_number":38,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":39,"context_line":""},{"line_number":40,"context_line":"We could extend the user API to support federated attributes. So for example,"},{"line_number":41,"context_line":"creating a federated user:"},{"line_number":42,"context_line":""}],"source_content_type":"text/x-rst","patch_set":7,"id":"7a77a97e_0c1d240f","line":39,"in_reply_to":"7a77a97e_5850c45e","updated":"2016-11-16 16:03:06.000000000","message":"No, this is not an enhancement to shadow mapping. It will simply allow operators to utilize the API to manage their domains, projects, users... as if they were local users.","commit_id":"b9d0c072002e80dfd3f82c1e3c8710673fd85fe2"},{"author":{"_account_id":17860,"name":"Samuel de Medeiros Queiroz","email":"samueldmq@gmail.com","username":"samueldmq"},"change_message_id":"8d043bb891d0ca7d8ab024d1b662ecc85ebb5479","unresolved":false,"context_lines":[{"line_number":78,"context_line":""},{"line_number":79,"context_line":"    GET /v3/users/?unique_id\u003d{unique_id}"},{"line_number":80,"context_line":""},{"line_number":81,"context_line":"This could go hand in hand with shadow mapping [2], allowing operators to"},{"line_number":82,"context_line":"bootstrap all of their users, as well as perform other common user operations,"},{"line_number":83,"context_line":"such as delegation via the API."},{"line_number":84,"context_line":""},{"line_number":85,"context_line":"Alternatives"},{"line_number":86,"context_line":"------------"}],"source_content_type":"text/x-rst","patch_set":7,"id":"7a77a97e_b804787e","line":83,"range":{"start_line":81,"start_character":0,"end_line":83,"end_character":31},"updated":"2016-11-16 13:24:04.000000000","message":"So this is not an alternative but an enhancement to the shadow mapping proposal","commit_id":"b9d0c072002e80dfd3f82c1e3c8710673fd85fe2"},{"author":{"_account_id":11022,"name":"Rodrigo Duarte Sousa","email":"rodrigodsousa@gmail.com","username":"rodrigods"},"change_message_id":"c0e0c3a56967a32f6815765528393a09b0a52b1b","unresolved":false,"context_lines":[{"line_number":8,"context_line":"Extend user API to support federated attributes"},{"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\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":10,"context_line":""},{"line_number":11,"context_line":"`bp support-federated-attr \u003chttps://blueprints.launchpad.net/keystone/+spec/support-federated-attr\u003e`_"},{"line_number":12,"context_line":""},{"line_number":13,"context_line":"Extend the user API to support federated attributes so that we treat federated"},{"line_number":14,"context_line":"users like any other keystone user."}],"source_content_type":"text/x-rst","patch_set":10,"id":"7a77a97e_bda0dc44","line":11,"range":{"start_line":11,"start_character":0,"end_line":11,"end_character":26},"updated":"2016-11-16 16:49:32.000000000","message":"could not find this bp","commit_id":"0b25bd102c3b91f4277131c13cb87d1779d5c5d3"},{"author":{"_account_id":6482,"name":"Steve Martinelli","email":"s.martinelli@gmail.com","username":"stevemar"},"change_message_id":"799a88ca51b4384328941ee45bd49c33cdae27eb","unresolved":false,"context_lines":[{"line_number":8,"context_line":"Extend user API to support federated attributes"},{"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\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":10,"context_line":""},{"line_number":11,"context_line":"`bp support-federated-attr \u003chttps://blueprints.launchpad.net/keystone/+spec/support-federated-attr\u003e`_"},{"line_number":12,"context_line":""},{"line_number":13,"context_line":"Extend the user API to support federated attributes so that we treat federated"},{"line_number":14,"context_line":"users like any other keystone user."}],"source_content_type":"text/x-rst","patch_set":10,"id":"7a77a97e_f3de036c","line":11,"range":{"start_line":11,"start_character":0,"end_line":11,"end_character":26},"in_reply_to":"7a77a97e_bda0dc44","updated":"2016-11-16 17:08:50.000000000","message":"we only create the bps after the spec has been approved.","commit_id":"0b25bd102c3b91f4277131c13cb87d1779d5c5d3"},{"author":{"_account_id":5046,"name":"Lance Bragstad","email":"lbragstad@redhat.com","username":"ldbragst"},"change_message_id":"66b0c8084951eea8e526b0ee03660ff045386ffd","unresolved":false,"context_lines":[{"line_number":22,"context_line":"assign a federated user a role, you would need the local user ID. Likewise, you"},{"line_number":23,"context_line":"would need the user ID to do delegation and create a trust. However, we don\u0027t"},{"line_number":24,"context_line":"have an API method that supports querying federated users in order to get the"},{"line_number":25,"context_line":"local user ID."},{"line_number":26,"context_line":""},{"line_number":27,"context_line":"Another question we have been dealing with, is how to provide authorization for"},{"line_number":28,"context_line":"federated users, since a federated user does not exist in keystone until they"}],"source_content_type":"text/x-rst","patch_set":12,"id":"7a77a97e_ff0afe88","line":25,"updated":"2016-11-18 00:18:23.000000000","message":"Wait - GET /v3/users/ doesn\u0027t return federated users?","commit_id":"1fdc359491986a6199799a3c2f29074312dceff7"},{"author":{"_account_id":18666,"name":"Chris Plock","email":"chrisplo@cisco.com","username":"plockc"},"change_message_id":"9a93b71049982e1340489c9abca489e8b13cfb3d","unresolved":false,"context_lines":[{"line_number":22,"context_line":"assign a federated user a role, you would need the local user ID. Likewise, you"},{"line_number":23,"context_line":"would need the user ID to do delegation and create a trust. However, we don\u0027t"},{"line_number":24,"context_line":"have an API method that supports querying federated users in order to get the"},{"line_number":25,"context_line":"local user ID."},{"line_number":26,"context_line":""},{"line_number":27,"context_line":"Another question we have been dealing with, is how to provide authorization for"},{"line_number":28,"context_line":"federated users, since a federated user does not exist in keystone until they"}],"source_content_type":"text/x-rst","patch_set":12,"id":"7a77a97e_7184440a","line":25,"in_reply_to":"7a77a97e_02a2fdfc","updated":"2016-11-18 15:45:49.000000000","message":"The attribute queries presented require a specific value to filter on, would there be a way to filter users that do or do not have any federated attributes? like ?federated\u003dtrue|false?","commit_id":"1fdc359491986a6199799a3c2f29074312dceff7"},{"author":{"_account_id":18338,"name":"Ron De Rose","email":"ronald.de.rose@intel.com","username":"derosenet"},"change_message_id":"c994aef209129fbe285f749f4dd50ebe4ff2bedd","unresolved":false,"context_lines":[{"line_number":22,"context_line":"assign a federated user a role, you would need the local user ID. Likewise, you"},{"line_number":23,"context_line":"would need the user ID to do delegation and create a trust. However, we don\u0027t"},{"line_number":24,"context_line":"have an API method that supports querying federated users in order to get the"},{"line_number":25,"context_line":"local user ID."},{"line_number":26,"context_line":""},{"line_number":27,"context_line":"Another question we have been dealing with, is how to provide authorization for"},{"line_number":28,"context_line":"federated users, since a federated user does not exist in keystone until they"}],"source_content_type":"text/x-rst","patch_set":12,"id":"7a77a97e_23feffad","line":25,"in_reply_to":"7a77a97e_7184440a","updated":"2016-11-18 16:01:12.000000000","message":"I haven\u0027t defined that here, but we could certainly support a query like that if needed.","commit_id":"1fdc359491986a6199799a3c2f29074312dceff7"},{"author":{"_account_id":18338,"name":"Ron De Rose","email":"ronald.de.rose@intel.com","username":"derosenet"},"change_message_id":"40df03b09f44994a7e409f7a79298d5342a5bed0","unresolved":false,"context_lines":[{"line_number":22,"context_line":"assign a federated user a role, you would need the local user ID. Likewise, you"},{"line_number":23,"context_line":"would need the user ID to do delegation and create a trust. However, we don\u0027t"},{"line_number":24,"context_line":"have an API method that supports querying federated users in order to get the"},{"line_number":25,"context_line":"local user ID."},{"line_number":26,"context_line":""},{"line_number":27,"context_line":"Another question we have been dealing with, is how to provide authorization for"},{"line_number":28,"context_line":"federated users, since a federated user does not exist in keystone until they"}],"source_content_type":"text/x-rst","patch_set":12,"id":"7a77a97e_02a2fdfc","line":25,"in_reply_to":"7a77a97e_ff0afe88","updated":"2016-11-18 00:46:01.000000000","message":"Yes, it does return federated users, but it would return all of your users; not a specific user because you are not able to filter on federated attributes.","commit_id":"1fdc359491986a6199799a3c2f29074312dceff7"},{"author":{"_account_id":5046,"name":"Lance Bragstad","email":"lbragstad@redhat.com","username":"ldbragst"},"change_message_id":"66b0c8084951eea8e526b0ee03660ff045386ffd","unresolved":false,"context_lines":[{"line_number":24,"context_line":"have an API method that supports querying federated users in order to get the"},{"line_number":25,"context_line":"local user ID."},{"line_number":26,"context_line":""},{"line_number":27,"context_line":"Another question we have been dealing with, is how to provide authorization for"},{"line_number":28,"context_line":"federated users, since a federated user does not exist in keystone until they"},{"line_number":29,"context_line":"authenticate for the first time. Shadow mapping [2] is an attempt to solve this"},{"line_number":30,"context_line":"by extending the mapping engine to automatically map users to projects and"}],"source_content_type":"text/x-rst","patch_set":12,"id":"7a77a97e_bfede6b8","line":27,"updated":"2016-11-18 00:18:23.000000000","message":"This paragraph highlights a valid concern, but I\u0027m not sure how it relates to extending the identity API to return federated attributes for federated users?","commit_id":"1fdc359491986a6199799a3c2f29074312dceff7"},{"author":{"_account_id":18338,"name":"Ron De Rose","email":"ronald.de.rose@intel.com","username":"derosenet"},"change_message_id":"5439eed78308c4d4ab653e2f404ed29f37252f68","unresolved":false,"context_lines":[{"line_number":24,"context_line":"have an API method that supports querying federated users in order to get the"},{"line_number":25,"context_line":"local user ID."},{"line_number":26,"context_line":""},{"line_number":27,"context_line":"Another question we have been dealing with, is how to provide authorization for"},{"line_number":28,"context_line":"federated users, since a federated user does not exist in keystone until they"},{"line_number":29,"context_line":"authenticate for the first time. Shadow mapping [2] is an attempt to solve this"},{"line_number":30,"context_line":"by extending the mapping engine to automatically map users to projects and"}],"source_content_type":"text/x-rst","patch_set":12,"id":"5a74a57a_c0f06269","line":27,"in_reply_to":"5a74a57a_49ee5aed","updated":"2016-12-01 04:07:44.000000000","message":"Modified this paragraph and removed the shadow mapping reference.","commit_id":"1fdc359491986a6199799a3c2f29074312dceff7"},{"author":{"_account_id":5046,"name":"Lance Bragstad","email":"lbragstad@redhat.com","username":"ldbragst"},"change_message_id":"bed526f79da76c7eb7660c3fa42eff592af94df4","unresolved":false,"context_lines":[{"line_number":24,"context_line":"have an API method that supports querying federated users in order to get the"},{"line_number":25,"context_line":"local user ID."},{"line_number":26,"context_line":""},{"line_number":27,"context_line":"Another question we have been dealing with, is how to provide authorization for"},{"line_number":28,"context_line":"federated users, since a federated user does not exist in keystone until they"},{"line_number":29,"context_line":"authenticate for the first time. Shadow mapping [2] is an attempt to solve this"},{"line_number":30,"context_line":"by extending the mapping engine to automatically map users to projects and"}],"source_content_type":"text/x-rst","patch_set":12,"id":"7a77a97e_6f7dede6","line":27,"in_reply_to":"7a77a97e_02f03dfd","updated":"2016-11-21 22:12:00.000000000","message":"Aha - I think I\u0027m following. This kind of relates to the question I had below, too. If keystone is the thing that is suppose to be creating shadow users during federated authentication, exposing federated user creation through the API feels like we pushing that back to the operators. \n\nIf an operator goes through and creates a federated user for something, and that federated user authenticates, does a second shadow user get created or does the shadow user logic take into account idp_id + unique_id + domain_id, etc?","commit_id":"1fdc359491986a6199799a3c2f29074312dceff7"},{"author":{"_account_id":7725,"name":"David Stanek","email":"dstanek@dstanek.com","username":"dstanek"},"change_message_id":"893b33e5a76e1cb6dc6964412fa189fb94eea950","unresolved":false,"context_lines":[{"line_number":24,"context_line":"have an API method that supports querying federated users in order to get the"},{"line_number":25,"context_line":"local user ID."},{"line_number":26,"context_line":""},{"line_number":27,"context_line":"Another question we have been dealing with, is how to provide authorization for"},{"line_number":28,"context_line":"federated users, since a federated user does not exist in keystone until they"},{"line_number":29,"context_line":"authenticate for the first time. Shadow mapping [2] is an attempt to solve this"},{"line_number":30,"context_line":"by extending the mapping engine to automatically map users to projects and"}],"source_content_type":"text/x-rst","patch_set":12,"id":"5a74a57a_49ee5aed","line":27,"in_reply_to":"7a77a97e_07ca6ba1","updated":"2016-11-30 15:59:43.000000000","message":"To me this is just a usecase to document and not a problem. The usecase is cloud operations need to get user id for their automatic provisioning processes. I wouldn\u0027t mention shadow mapping because it\u0027s not relevant.","commit_id":"1fdc359491986a6199799a3c2f29074312dceff7"},{"author":{"_account_id":18338,"name":"Ron De Rose","email":"ronald.de.rose@intel.com","username":"derosenet"},"change_message_id":"90a3f6323bcd10b6570042b186c6abc9f8207f50","unresolved":false,"context_lines":[{"line_number":24,"context_line":"have an API method that supports querying federated users in order to get the"},{"line_number":25,"context_line":"local user ID."},{"line_number":26,"context_line":""},{"line_number":27,"context_line":"Another question we have been dealing with, is how to provide authorization for"},{"line_number":28,"context_line":"federated users, since a federated user does not exist in keystone until they"},{"line_number":29,"context_line":"authenticate for the first time. Shadow mapping [2] is an attempt to solve this"},{"line_number":30,"context_line":"by extending the mapping engine to automatically map users to projects and"}],"source_content_type":"text/x-rst","patch_set":12,"id":"7a77a97e_07ca6ba1","line":27,"in_reply_to":"7a77a97e_6f7dede6","updated":"2016-11-22 19:52:14.000000000","message":"Yeah, shadow users checks if the federated user exists (idp_id, protocol_id, unique_id) and if so, returns that user.\n\nI don\u0027t think of it as pushing it back to the operators, so much as giving them more flexibility; allowing them to utilize the user API to do user operations, including mapping their federated users to local identities (user create).","commit_id":"1fdc359491986a6199799a3c2f29074312dceff7"},{"author":{"_account_id":18338,"name":"Ron De Rose","email":"ronald.de.rose@intel.com","username":"derosenet"},"change_message_id":"40df03b09f44994a7e409f7a79298d5342a5bed0","unresolved":false,"context_lines":[{"line_number":24,"context_line":"have an API method that supports querying federated users in order to get the"},{"line_number":25,"context_line":"local user ID."},{"line_number":26,"context_line":""},{"line_number":27,"context_line":"Another question we have been dealing with, is how to provide authorization for"},{"line_number":28,"context_line":"federated users, since a federated user does not exist in keystone until they"},{"line_number":29,"context_line":"authenticate for the first time. Shadow mapping [2] is an attempt to solve this"},{"line_number":30,"context_line":"by extending the mapping engine to automatically map users to projects and"}],"source_content_type":"text/x-rst","patch_set":12,"id":"7a77a97e_02f03dfd","line":27,"in_reply_to":"7a77a97e_bfede6b8","updated":"2016-11-18 00:46:01.000000000","message":"By extending the API, operators could use the API to provision authorization for federated users. So it\u0027s not just about returning federated attributes, but also allowing operators to create federated users via the API and then make concrete role assignments.\n\nThe reason why I mention the concern, is that this could be an alternative to shadow mapping provisioning. That being said, rather than an alternative, I see this going hand-in-hand with shadow mapping. Shadow mapping allows for provisioning in mass. While extending the API, allows for other common user operations, such as delegation.","commit_id":"1fdc359491986a6199799a3c2f29074312dceff7"},{"author":{"_account_id":5046,"name":"Lance Bragstad","email":"lbragstad@redhat.com","username":"ldbragst"},"change_message_id":"66b0c8084951eea8e526b0ee03660ff045386ffd","unresolved":false,"context_lines":[{"line_number":43,"context_line":""},{"line_number":44,"context_line":".. code:: javascript"},{"line_number":45,"context_line":""},{"line_number":46,"context_line":"    POST /v3/users"},{"line_number":47,"context_line":"    {"},{"line_number":48,"context_line":"        \"user\": {"},{"line_number":49,"context_line":"            \"default_project_id\": \"263fd9\","}],"source_content_type":"text/x-rst","patch_set":12,"id":"7a77a97e_7f250e07","line":46,"updated":"2016-11-18 00:18:23.000000000","message":"Do we want to open this up initially, or do we only want the shadow user api to get post requests when a federated user has successfully authenticated?\n\nIt seems like the problem statement would be solved by extending GET /v3/users/ and GET /v3/users/{shadow_user_id}/ to return federated attributes.","commit_id":"1fdc359491986a6199799a3c2f29074312dceff7"},{"author":{"_account_id":5046,"name":"Lance Bragstad","email":"lbragstad@redhat.com","username":"ldbragst"},"change_message_id":"57bd7de434a6e71a9d6c7bdceae82e5d03ce038b","unresolved":false,"context_lines":[{"line_number":43,"context_line":""},{"line_number":44,"context_line":".. code:: javascript"},{"line_number":45,"context_line":""},{"line_number":46,"context_line":"    POST /v3/users"},{"line_number":47,"context_line":"    {"},{"line_number":48,"context_line":"        \"user\": {"},{"line_number":49,"context_line":"            \"default_project_id\": \"263fd9\","}],"source_content_type":"text/x-rst","patch_set":12,"id":"5a74a57a_64ef211e","line":46,"in_reply_to":"5a74a57a_10d6ac27","updated":"2016-11-28 22:43:46.000000000","message":"Aha, so the operator has to supply that to the federated user after they do the provisioning manually?","commit_id":"1fdc359491986a6199799a3c2f29074312dceff7"},{"author":{"_account_id":18338,"name":"Ron De Rose","email":"ronald.de.rose@intel.com","username":"derosenet"},"change_message_id":"b7db0bbc86e3ee31373d46f488b8477b9b9b95cc","unresolved":false,"context_lines":[{"line_number":43,"context_line":""},{"line_number":44,"context_line":".. code:: javascript"},{"line_number":45,"context_line":""},{"line_number":46,"context_line":"    POST /v3/users"},{"line_number":47,"context_line":"    {"},{"line_number":48,"context_line":"        \"user\": {"},{"line_number":49,"context_line":"            \"default_project_id\": \"263fd9\","}],"source_content_type":"text/x-rst","patch_set":12,"id":"5a74a57a_5a059e0e","line":46,"in_reply_to":"5a74a57a_64ef211e","updated":"2016-11-28 23:45:13.000000000","message":"No, the operator would supply the federated attributes, such as unique_id and Keystone would generate the user ID.","commit_id":"1fdc359491986a6199799a3c2f29074312dceff7"},{"author":{"_account_id":18338,"name":"Ron De Rose","email":"ronald.de.rose@intel.com","username":"derosenet"},"change_message_id":"b711d4e9596b3cb5a25a35c7ffd4d66dc85a5014","unresolved":false,"context_lines":[{"line_number":43,"context_line":""},{"line_number":44,"context_line":".. code:: javascript"},{"line_number":45,"context_line":""},{"line_number":46,"context_line":"    POST /v3/users"},{"line_number":47,"context_line":"    {"},{"line_number":48,"context_line":"        \"user\": {"},{"line_number":49,"context_line":"            \"default_project_id\": \"263fd9\","}],"source_content_type":"text/x-rst","patch_set":12,"id":"5a74a57a_10d6ac27","line":46,"in_reply_to":"5a74a57a_efb86f13","updated":"2016-11-28 22:11:51.000000000","message":"Currently, the user ID for a federated user is a uuid:\nhttps://github.com/openstack/keystone/blob/master/keystone/identity/shadow_backends/sql.py#L33","commit_id":"1fdc359491986a6199799a3c2f29074312dceff7"},{"author":{"_account_id":5046,"name":"Lance Bragstad","email":"lbragstad@redhat.com","username":"ldbragst"},"change_message_id":"bed526f79da76c7eb7660c3fa42eff592af94df4","unresolved":false,"context_lines":[{"line_number":43,"context_line":""},{"line_number":44,"context_line":".. code:: javascript"},{"line_number":45,"context_line":""},{"line_number":46,"context_line":"    POST /v3/users"},{"line_number":47,"context_line":"    {"},{"line_number":48,"context_line":"        \"user\": {"},{"line_number":49,"context_line":"            \"default_project_id\": \"263fd9\","}],"source_content_type":"text/x-rst","patch_set":12,"id":"7a77a97e_cf7b6128","line":46,"in_reply_to":"7a77a97e_62c6519b","updated":"2016-11-21 22:12:00.000000000","message":"True - they are. I was just thinking about if it made sense to have a formal (external) API for creating federated users. One of the main use cases for shadow users was so that keystone could handle the creation of a shell user for operators. Here it seems like we\u0027re putting that responsibility back on the operator, instead of leveraging keystone for it. Does that help clarify my question?","commit_id":"1fdc359491986a6199799a3c2f29074312dceff7"},{"author":{"_account_id":18338,"name":"Ron De Rose","email":"ronald.de.rose@intel.com","username":"derosenet"},"change_message_id":"40df03b09f44994a7e409f7a79298d5342a5bed0","unresolved":false,"context_lines":[{"line_number":43,"context_line":""},{"line_number":44,"context_line":".. code:: javascript"},{"line_number":45,"context_line":""},{"line_number":46,"context_line":"    POST /v3/users"},{"line_number":47,"context_line":"    {"},{"line_number":48,"context_line":"        \"user\": {"},{"line_number":49,"context_line":"            \"default_project_id\": \"263fd9\","}],"source_content_type":"text/x-rst","patch_set":12,"id":"7a77a97e_62c6519b","line":46,"in_reply_to":"7a77a97e_7f250e07","updated":"2016-11-18 00:46:01.000000000","message":"I like the idea of opening it up and treating federated users like any other user.\n\nI\u0027m not following \"/v3/users/{shadow_user_id}/\". The shadow_user_id and user_id are the same things.","commit_id":"1fdc359491986a6199799a3c2f29074312dceff7"},{"author":{"_account_id":18338,"name":"Ron De Rose","email":"ronald.de.rose@intel.com","username":"derosenet"},"change_message_id":"90a3f6323bcd10b6570042b186c6abc9f8207f50","unresolved":false,"context_lines":[{"line_number":43,"context_line":""},{"line_number":44,"context_line":".. code:: javascript"},{"line_number":45,"context_line":""},{"line_number":46,"context_line":"    POST /v3/users"},{"line_number":47,"context_line":"    {"},{"line_number":48,"context_line":"        \"user\": {"},{"line_number":49,"context_line":"            \"default_project_id\": \"263fd9\","}],"source_content_type":"text/x-rst","patch_set":12,"id":"7a77a97e_e27b9df2","line":46,"in_reply_to":"7a77a97e_cf7b6128","updated":"2016-11-22 19:52:14.000000000","message":"It does and it\u0027s a good point. However, if it makes sense to support federated attributes for returning federated users, and there is a strong argument for that, then it seems reasonable to support create as well.\n\nI think when operators want to provision in mass, they\u0027ll utilize shadow mapping. When operators want to provision on demand, e.g. 1) user request access, 2) manager approves request, 3) assign role to user, they\u0027ll be able to use the API as an option.\n\nAnd to me, it simply gives operators greater flexibility, and ultimately get us to treating a federated user like any other Keystone user.","commit_id":"1fdc359491986a6199799a3c2f29074312dceff7"},{"author":{"_account_id":5046,"name":"Lance Bragstad","email":"lbragstad@redhat.com","username":"ldbragst"},"change_message_id":"2fa8e1b896fe6c421b41fdeb60b6cedb79af0657","unresolved":false,"context_lines":[{"line_number":43,"context_line":""},{"line_number":44,"context_line":".. code:: javascript"},{"line_number":45,"context_line":""},{"line_number":46,"context_line":"    POST /v3/users"},{"line_number":47,"context_line":"    {"},{"line_number":48,"context_line":"        \"user\": {"},{"line_number":49,"context_line":"            \"default_project_id\": \"263fd9\","}],"source_content_type":"text/x-rst","patch_set":12,"id":"5a74a57a_efb86f13","line":46,"in_reply_to":"7a77a97e_e27b9df2","updated":"2016-11-28 20:53:57.000000000","message":"So - regardless of whether a federated user is created using the shadow mapping or the identity API, the ID of the federated user is computed based on a combination of idp_id, protocol_id, and domain_id (or some set of federated attributes)?\n\nIf operators choose to provision federated users on demand, do they need to do so in a way that produces an expected user id (i.e. a hash of this domain_id, idp_id, and protocol_id, will be this shadow user id use case)?","commit_id":"1fdc359491986a6199799a3c2f29074312dceff7"},{"author":{"_account_id":7725,"name":"David Stanek","email":"dstanek@dstanek.com","username":"dstanek"},"change_message_id":"893b33e5a76e1cb6dc6964412fa189fb94eea950","unresolved":false,"context_lines":[{"line_number":50,"context_line":"            \"domain_id\": \"1789d1\","},{"line_number":51,"context_line":"            \"enabled\": true,"},{"line_number":52,"context_line":"            \"name\": \"James Doe\","},{"line_number":53,"context_line":"            \"federated\": {"},{"line_number":54,"context_line":"                \"idp_id\": \"1789d1\","},{"line_number":55,"context_line":"                \"protocol_id\": saml2,"},{"line_number":56,"context_line":"                \"unique_id\": \"jdoe\","}],"source_content_type":"text/x-rst","patch_set":12,"id":"5a74a57a_e97646d7","line":53,"updated":"2016-11-30 15:59:43.000000000","message":"Does this come back when getting a user? Or maybe better do we get a link to this subresource?","commit_id":"1fdc359491986a6199799a3c2f29074312dceff7"},{"author":{"_account_id":2218,"name":"Adam Young","email":"adam@younglogic.com","username":"ayoung"},"change_message_id":"69b142bff9351e119b3b3ee511ed96f4293fa1fa","unresolved":false,"context_lines":[{"line_number":50,"context_line":"            \"domain_id\": \"1789d1\","},{"line_number":51,"context_line":"            \"enabled\": true,"},{"line_number":52,"context_line":"            \"name\": \"James Doe\","},{"line_number":53,"context_line":"            \"federated\": {"},{"line_number":54,"context_line":"                \"idp_id\": \"1789d1\","},{"line_number":55,"context_line":"                \"protocol_id\": saml2,"},{"line_number":56,"context_line":"                \"unique_id\": \"jdoe\","}],"source_content_type":"text/x-rst","patch_set":12,"id":"5a74a57a_d1391ea5","line":53,"in_reply_to":"5a74a57a_447e41af","updated":"2016-12-01 00:42:29.000000000","message":"This needs to support multiple.  Also, it should require a special parameter to get this information, otherwise we risk breaking people bty changing the format of the returned data.","commit_id":"1fdc359491986a6199799a3c2f29074312dceff7"},{"author":{"_account_id":18338,"name":"Ron De Rose","email":"ronald.de.rose@intel.com","username":"derosenet"},"change_message_id":"5439eed78308c4d4ab653e2f404ed29f37252f68","unresolved":false,"context_lines":[{"line_number":50,"context_line":"            \"domain_id\": \"1789d1\","},{"line_number":51,"context_line":"            \"enabled\": true,"},{"line_number":52,"context_line":"            \"name\": \"James Doe\","},{"line_number":53,"context_line":"            \"federated\": {"},{"line_number":54,"context_line":"                \"idp_id\": \"1789d1\","},{"line_number":55,"context_line":"                \"protocol_id\": saml2,"},{"line_number":56,"context_line":"                \"unique_id\": \"jdoe\","}],"source_content_type":"text/x-rst","patch_set":12,"id":"5a74a57a_c09782e9","line":53,"in_reply_to":"5a74a57a_d1391ea5","updated":"2016-12-01 04:07:44.000000000","message":"Done","commit_id":"1fdc359491986a6199799a3c2f29074312dceff7"},{"author":{"_account_id":18338,"name":"Ron De Rose","email":"ronald.de.rose@intel.com","username":"derosenet"},"change_message_id":"870dc68914c80bca8026f8aef1ea6e7066381a21","unresolved":false,"context_lines":[{"line_number":50,"context_line":"            \"domain_id\": \"1789d1\","},{"line_number":51,"context_line":"            \"enabled\": true,"},{"line_number":52,"context_line":"            \"name\": \"James Doe\","},{"line_number":53,"context_line":"            \"federated\": {"},{"line_number":54,"context_line":"                \"idp_id\": \"1789d1\","},{"line_number":55,"context_line":"                \"protocol_id\": saml2,"},{"line_number":56,"context_line":"                \"unique_id\": \"jdoe\","}],"source_content_type":"text/x-rst","patch_set":12,"id":"5a74a57a_447e41af","line":53,"in_reply_to":"5a74a57a_e97646d7","updated":"2016-11-30 16:18:20.000000000","message":"This would come back when getting a user. So you would get a link to the resource, which would include the sub-resource.","commit_id":"1fdc359491986a6199799a3c2f29074312dceff7"},{"author":{"_account_id":7725,"name":"David Stanek","email":"dstanek@dstanek.com","username":"dstanek"},"change_message_id":"893b33e5a76e1cb6dc6964412fa189fb94eea950","unresolved":false,"context_lines":[{"line_number":63,"context_line":""},{"line_number":64,"context_line":".. code:: javascript"},{"line_number":65,"context_line":""},{"line_number":66,"context_line":"    POST /v3/users/{id}/federated"},{"line_number":67,"context_line":"    {"},{"line_number":68,"context_line":"        \"federated\": {"},{"line_number":69,"context_line":"            \"idp_id\": \"1789d1\","}],"source_content_type":"text/x-rst","patch_set":12,"id":"5a74a57a_29e59ea7","line":66,"updated":"2016-11-30 15:59:43.000000000","message":"I\u0027m on the fence about POST vs. PUT here. What comes back on a GET for this resource?","commit_id":"1fdc359491986a6199799a3c2f29074312dceff7"},{"author":{"_account_id":18338,"name":"Ron De Rose","email":"ronald.de.rose@intel.com","username":"derosenet"},"change_message_id":"870dc68914c80bca8026f8aef1ea6e7066381a21","unresolved":false,"context_lines":[{"line_number":63,"context_line":""},{"line_number":64,"context_line":".. code:: javascript"},{"line_number":65,"context_line":""},{"line_number":66,"context_line":"    POST /v3/users/{id}/federated"},{"line_number":67,"context_line":"    {"},{"line_number":68,"context_line":"        \"federated\": {"},{"line_number":69,"context_line":"            \"idp_id\": \"1789d1\","}],"source_content_type":"text/x-rst","patch_set":12,"id":"5a74a57a_dfcdbc87","line":66,"in_reply_to":"5a74a57a_29e59ea7","updated":"2016-11-30 16:18:20.000000000","message":"I think this example should be PUT. The GET response should return a federated object.","commit_id":"1fdc359491986a6199799a3c2f29074312dceff7"},{"author":{"_account_id":18338,"name":"Ron De Rose","email":"ronald.de.rose@intel.com","username":"derosenet"},"change_message_id":"5439eed78308c4d4ab653e2f404ed29f37252f68","unresolved":false,"context_lines":[{"line_number":63,"context_line":""},{"line_number":64,"context_line":".. code:: javascript"},{"line_number":65,"context_line":""},{"line_number":66,"context_line":"    POST /v3/users/{id}/federated"},{"line_number":67,"context_line":"    {"},{"line_number":68,"context_line":"        \"federated\": {"},{"line_number":69,"context_line":"            \"idp_id\": \"1789d1\","}],"source_content_type":"text/x-rst","patch_set":12,"id":"5a74a57a_d4fe6704","line":66,"in_reply_to":"5a74a57a_9167a6b6","updated":"2016-12-01 04:07:44.000000000","message":"I\u0027ve updated the POST and PUT accordingly.\n\nThe federated object is based on the federated_user data model, which is everything we need to create a federated user.  Having a section for protocol specific data, as we have in the token request, could overly complicate the request and I\u0027m not clear as to why this would be needed.","commit_id":"1fdc359491986a6199799a3c2f29074312dceff7"},{"author":{"_account_id":2218,"name":"Adam Young","email":"adam@younglogic.com","username":"ayoung"},"change_message_id":"69b142bff9351e119b3b3ee511ed96f4293fa1fa","unresolved":false,"context_lines":[{"line_number":63,"context_line":""},{"line_number":64,"context_line":".. code:: javascript"},{"line_number":65,"context_line":""},{"line_number":66,"context_line":"    POST /v3/users/{id}/federated"},{"line_number":67,"context_line":"    {"},{"line_number":68,"context_line":"        \"federated\": {"},{"line_number":69,"context_line":"            \"idp_id\": \"1789d1\","}],"source_content_type":"text/x-rst","patch_set":12,"id":"5a74a57a_9167a6b6","line":66,"in_reply_to":"5a74a57a_dfcdbc87","updated":"2016-12-01 00:42:29.000000000","message":"When we do not have an ID ahead of time, I think it needs to be a post.  But in this case, the URL uniqely identifies the user and is acceptable, so it should be a PUT.\n\nMake a section under the block for the protocol specific data, like we have for token request.  it the protocol is SAML make it a SAML block.  The values in here should be the pre-mapped environment variables that would be passed through from the Apache mode, and thus should not be limited to just \"unique_id\".\n\nTO see the range of the variables we need to suppor,t look here.\n\nhttp://www.freeipa.org/page/Environment_Variables","commit_id":"1fdc359491986a6199799a3c2f29074312dceff7"},{"author":{"_account_id":7725,"name":"David Stanek","email":"dstanek@dstanek.com","username":"dstanek"},"change_message_id":"893b33e5a76e1cb6dc6964412fa189fb94eea950","unresolved":false,"context_lines":[{"line_number":84,"context_line":"            \"name\": \"James Doe\","},{"line_number":85,"context_line":"            \"enabled\": true,"},{"line_number":86,"context_line":"            \"links\": {"},{"line_number":87,"context_line":"                \"self\": \"https://example.com/identity/v3/users/9fe1d3\""},{"line_number":88,"context_line":"            }"},{"line_number":89,"context_line":"        }"},{"line_number":90,"context_line":"    }"}],"source_content_type":"text/x-rst","patch_set":12,"id":"5a74a57a_89ba32bf","line":87,"updated":"2016-11-30 15:59:43.000000000","message":"Wouldn\u0027t self be a link to /v3/users/{id}/federated and a new link for \u0027user\u0027 be created?","commit_id":"1fdc359491986a6199799a3c2f29074312dceff7"},{"author":{"_account_id":18338,"name":"Ron De Rose","email":"ronald.de.rose@intel.com","username":"derosenet"},"change_message_id":"870dc68914c80bca8026f8aef1ea6e7066381a21","unresolved":false,"context_lines":[{"line_number":84,"context_line":"            \"name\": \"James Doe\","},{"line_number":85,"context_line":"            \"enabled\": true,"},{"line_number":86,"context_line":"            \"links\": {"},{"line_number":87,"context_line":"                \"self\": \"https://example.com/identity/v3/users/9fe1d3\""},{"line_number":88,"context_line":"            }"},{"line_number":89,"context_line":"        }"},{"line_number":90,"context_line":"    }"}],"source_content_type":"text/x-rst","patch_set":12,"id":"5a74a57a_3f5f900f","line":87,"in_reply_to":"5a74a57a_89ba32bf","updated":"2016-11-30 16:18:20.000000000","message":"Yes, you are right, it should.","commit_id":"1fdc359491986a6199799a3c2f29074312dceff7"},{"author":{"_account_id":5046,"name":"Lance Bragstad","email":"lbragstad@redhat.com","username":"ldbragst"},"change_message_id":"66b0c8084951eea8e526b0ee03660ff045386ffd","unresolved":false,"context_lines":[{"line_number":94,"context_line":""},{"line_number":95,"context_line":".. code:: javascript"},{"line_number":96,"context_line":""},{"line_number":97,"context_line":"    GET /v3/users/?unique_id\u003d{unique_id}"},{"line_number":98,"context_line":""},{"line_number":99,"context_line":"If the unique_id was not unique across the organization, the request would need"},{"line_number":100,"context_line":"to include the domain_id in order to return the specific user."}],"source_content_type":"text/x-rst","patch_set":12,"id":"7a77a97e_df7aa2f0","line":97,"updated":"2016-11-18 00:18:23.000000000","message":"What\u0027s the difference between the unique_id and the id? For shadow users, isn\u0027t the unique id generated from a combination of idp, domain, etc... If so, why not just do:\n\n  GET /v3/users/{unique_id} \n\nJust like how we get information specific to a single user today?","commit_id":"1fdc359491986a6199799a3c2f29074312dceff7"},{"author":{"_account_id":18666,"name":"Chris Plock","email":"chrisplo@cisco.com","username":"plockc"},"change_message_id":"3f2366bd38287b9bc782d4ee0eaf1750b7b9c72c","unresolved":false,"context_lines":[{"line_number":94,"context_line":""},{"line_number":95,"context_line":".. code:: javascript"},{"line_number":96,"context_line":""},{"line_number":97,"context_line":"    GET /v3/users/?unique_id\u003d{unique_id}"},{"line_number":98,"context_line":""},{"line_number":99,"context_line":"If the unique_id was not unique across the organization, the request would need"},{"line_number":100,"context_line":"to include the domain_id in order to return the specific user."}],"source_content_type":"text/x-rst","patch_set":12,"id":"7a77a97e_825d2d49","line":97,"in_reply_to":"7a77a97e_42b795f4","updated":"2016-11-18 01:02:48.000000000","message":"Seems like the above would want to returns a list of users across all IdPs and protocols that have the same unique_id?","commit_id":"1fdc359491986a6199799a3c2f29074312dceff7"},{"author":{"_account_id":18338,"name":"Ron De Rose","email":"ronald.de.rose@intel.com","username":"derosenet"},"change_message_id":"f309a143c8f180014bed35968dec6872cfc84d08","unresolved":false,"context_lines":[{"line_number":94,"context_line":""},{"line_number":95,"context_line":".. code:: javascript"},{"line_number":96,"context_line":""},{"line_number":97,"context_line":"    GET /v3/users/?unique_id\u003d{unique_id}"},{"line_number":98,"context_line":""},{"line_number":99,"context_line":"If the unique_id was not unique across the organization, the request would need"},{"line_number":100,"context_line":"to include the domain_id in order to return the specific user."}],"source_content_type":"text/x-rst","patch_set":12,"id":"7a77a97e_d500c103","line":97,"in_reply_to":"7a77a97e_825d2d49","updated":"2016-11-18 01:09:33.000000000","message":"Yeah, if the same unique_id existed in other IdPs, it would return a list of users. However, if the unique_id was prefixed with the domain, then it would be unique across IdPs and return a single user.","commit_id":"1fdc359491986a6199799a3c2f29074312dceff7"},{"author":{"_account_id":5046,"name":"Lance Bragstad","email":"lbragstad@redhat.com","username":"ldbragst"},"change_message_id":"c04538c291d3afdf940b131b396cebb02491b2e9","unresolved":false,"context_lines":[{"line_number":94,"context_line":""},{"line_number":95,"context_line":".. code:: javascript"},{"line_number":96,"context_line":""},{"line_number":97,"context_line":"    GET /v3/users/?unique_id\u003d{unique_id}"},{"line_number":98,"context_line":""},{"line_number":99,"context_line":"If the unique_id was not unique across the organization, the request would need"},{"line_number":100,"context_line":"to include the domain_id in order to return the specific user."}],"source_content_type":"text/x-rst","patch_set":12,"id":"3a71b18c_6642b3af","line":97,"in_reply_to":"7a77a97e_d500c103","updated":"2016-12-07 02:37:26.000000000","message":"Aha - got it, that makes sense.","commit_id":"1fdc359491986a6199799a3c2f29074312dceff7"},{"author":{"_account_id":18338,"name":"Ron De Rose","email":"ronald.de.rose@intel.com","username":"derosenet"},"change_message_id":"40df03b09f44994a7e409f7a79298d5342a5bed0","unresolved":false,"context_lines":[{"line_number":94,"context_line":""},{"line_number":95,"context_line":".. code:: javascript"},{"line_number":96,"context_line":""},{"line_number":97,"context_line":"    GET /v3/users/?unique_id\u003d{unique_id}"},{"line_number":98,"context_line":""},{"line_number":99,"context_line":"If the unique_id was not unique across the organization, the request would need"},{"line_number":100,"context_line":"to include the domain_id in order to return the specific user."}],"source_content_type":"text/x-rst","patch_set":12,"id":"7a77a97e_42b795f4","line":97,"in_reply_to":"7a77a97e_df7aa2f0","updated":"2016-11-18 00:46:01.000000000","message":"unique_id is the IdP\u0027s unique identifier for that user. It\u0027s not generated by Keystone, but passed in from the IdP. It may or may not be prefixed with the domain, it\u0027s up to the IdP, but it should be unique within the domain (IdP).","commit_id":"1fdc359491986a6199799a3c2f29074312dceff7"},{"author":{"_account_id":18666,"name":"Chris Plock","email":"chrisplo@cisco.com","username":"plockc"},"change_message_id":"3f2366bd38287b9bc782d4ee0eaf1750b7b9c72c","unresolved":false,"context_lines":[{"line_number":97,"context_line":"    GET /v3/users/?unique_id\u003d{unique_id}"},{"line_number":98,"context_line":""},{"line_number":99,"context_line":"If the unique_id was not unique across the organization, the request would need"},{"line_number":100,"context_line":"to include the domain_id in order to return the specific user."},{"line_number":101,"context_line":""},{"line_number":102,"context_line":"Extending the API, could go hand in hand with shadow mapping [2], allowing"},{"line_number":103,"context_line":"operators to bootstrap all of their users, as well as perform other common user"}],"source_content_type":"text/x-rst","patch_set":12,"id":"7a77a97e_c2a8057a","line":100,"updated":"2016-11-18 01:02:48.000000000","message":"that doesn\u0027t seem to be specific enough to get to a single user?","commit_id":"1fdc359491986a6199799a3c2f29074312dceff7"},{"author":{"_account_id":18338,"name":"Ron De Rose","email":"ronald.de.rose@intel.com","username":"derosenet"},"change_message_id":"90a3f6323bcd10b6570042b186c6abc9f8207f50","unresolved":false,"context_lines":[{"line_number":97,"context_line":"    GET /v3/users/?unique_id\u003d{unique_id}"},{"line_number":98,"context_line":""},{"line_number":99,"context_line":"If the unique_id was not unique across the organization, the request would need"},{"line_number":100,"context_line":"to include the domain_id in order to return the specific user."},{"line_number":101,"context_line":""},{"line_number":102,"context_line":"Extending the API, could go hand in hand with shadow mapping [2], allowing"},{"line_number":103,"context_line":"operators to bootstrap all of their users, as well as perform other common user"}],"source_content_type":"text/x-rst","patch_set":12,"id":"7a77a97e_5dcc3661","line":100,"in_reply_to":"7a77a97e_71436413","updated":"2016-11-22 19:52:14.000000000","message":"Yeah, my intent is any combination of federated attributes, but we\u0027ll likely start with a subset. Prefixing may be a good approach, however we can solve this during the development.","commit_id":"1fdc359491986a6199799a3c2f29074312dceff7"},{"author":{"_account_id":18666,"name":"Chris Plock","email":"chrisplo@cisco.com","username":"plockc"},"change_message_id":"f8f5195d1301a8a4903987837abe446281c2ef57","unresolved":false,"context_lines":[{"line_number":97,"context_line":"    GET /v3/users/?unique_id\u003d{unique_id}"},{"line_number":98,"context_line":""},{"line_number":99,"context_line":"If the unique_id was not unique across the organization, the request would need"},{"line_number":100,"context_line":"to include the domain_id in order to return the specific user."},{"line_number":101,"context_line":""},{"line_number":102,"context_line":"Extending the API, could go hand in hand with shadow mapping [2], allowing"},{"line_number":103,"context_line":"operators to bootstrap all of their users, as well as perform other common user"}],"source_content_type":"text/x-rst","patch_set":12,"id":"7a77a97e_ced10e59","line":100,"in_reply_to":"7a77a97e_b55d0517","updated":"2016-11-18 03:03:44.000000000","message":"I found this: https://bugs.launchpad.net/keystone/+bug/1642687, which I guess is part of http://specs.openstack.org/openstack/keystone-specs/specs/keystone/ocata/shadow-mapping.html, \"The mapping explicitly references a domain_id\" which I take means it will be required going forward?\n\nI haven\u0027t found anything in specs \"shadow-mapping\", \"shadow-users\", or \"shadow-users-newton\" that says there is a 1:1 mapping between (IdP+protocol) -\u003e domain, (like I would have expected I could map multiple IdPs to a single domain) am I missing a spec?","commit_id":"1fdc359491986a6199799a3c2f29074312dceff7"},{"author":{"_account_id":18338,"name":"Ron De Rose","email":"ronald.de.rose@intel.com","username":"derosenet"},"change_message_id":"f309a143c8f180014bed35968dec6872cfc84d08","unresolved":false,"context_lines":[{"line_number":97,"context_line":"    GET /v3/users/?unique_id\u003d{unique_id}"},{"line_number":98,"context_line":""},{"line_number":99,"context_line":"If the unique_id was not unique across the organization, the request would need"},{"line_number":100,"context_line":"to include the domain_id in order to return the specific user."},{"line_number":101,"context_line":""},{"line_number":102,"context_line":"Extending the API, could go hand in hand with shadow mapping [2], allowing"},{"line_number":103,"context_line":"operators to bootstrap all of their users, as well as perform other common user"}],"source_content_type":"text/x-rst","patch_set":12,"id":"7a77a97e_b55d0517","line":100,"in_reply_to":"7a77a97e_c2a8057a","updated":"2016-11-18 01:09:33.000000000","message":"An IdP should be mapped to a domain, so if you include the domain_id, it should be enough to get a single user.","commit_id":"1fdc359491986a6199799a3c2f29074312dceff7"},{"author":{"_account_id":18338,"name":"Ron De Rose","email":"ronald.de.rose@intel.com","username":"derosenet"},"change_message_id":"9b56d1971b7027e2a67d46de498d2829fb89b1e8","unresolved":false,"context_lines":[{"line_number":97,"context_line":"    GET /v3/users/?unique_id\u003d{unique_id}"},{"line_number":98,"context_line":""},{"line_number":99,"context_line":"If the unique_id was not unique across the organization, the request would need"},{"line_number":100,"context_line":"to include the domain_id in order to return the specific user."},{"line_number":101,"context_line":""},{"line_number":102,"context_line":"Extending the API, could go hand in hand with shadow mapping [2], allowing"},{"line_number":103,"context_line":"operators to bootstrap all of their users, as well as perform other common user"}],"source_content_type":"text/x-rst","patch_set":12,"id":"7a77a97e_eeade7e9","line":100,"in_reply_to":"7a77a97e_ced10e59","updated":"2016-11-18 05:32:43.000000000","message":"The intent has always been a 1:1 mapping; I have a patch here to change the API to require a domain_id when registering an IdP:\nhttps://review.openstack.org/#/c/399157/\n\nHowever technically, you\u0027re correct, you could map multiple IdPs to the same domain. In that case, you\u0027d have to include the idp_id in the query to return a single user.","commit_id":"1fdc359491986a6199799a3c2f29074312dceff7"},{"author":{"_account_id":18666,"name":"Chris Plock","email":"chrisplo@cisco.com","username":"plockc"},"change_message_id":"9a93b71049982e1340489c9abca489e8b13cfb3d","unresolved":false,"context_lines":[{"line_number":97,"context_line":"    GET /v3/users/?unique_id\u003d{unique_id}"},{"line_number":98,"context_line":""},{"line_number":99,"context_line":"If the unique_id was not unique across the organization, the request would need"},{"line_number":100,"context_line":"to include the domain_id in order to return the specific user."},{"line_number":101,"context_line":""},{"line_number":102,"context_line":"Extending the API, could go hand in hand with shadow mapping [2], allowing"},{"line_number":103,"context_line":"operators to bootstrap all of their users, as well as perform other common user"}],"source_content_type":"text/x-rst","patch_set":12,"id":"7a77a97e_71436413","line":100,"in_reply_to":"7a77a97e_eeade7e9","updated":"2016-11-18 15:45:49.000000000","message":"Ah thanks, though the wording (and the name unique_id) suggests we\u0027re doing unique lookups, while it seems to me these are filters and that\u0027s an important distinction to make.\n\nShould we make it clear that you can use any combination of the federated attributes in a query?\n\nShould we prefix the attributes in the query with \"federated_\"?  The exampe query above looks like it could be confused with a non-federated attribute.\n\nThanks","commit_id":"1fdc359491986a6199799a3c2f29074312dceff7"},{"author":{"_account_id":7725,"name":"David Stanek","email":"dstanek@dstanek.com","username":"dstanek"},"change_message_id":"893b33e5a76e1cb6dc6964412fa189fb94eea950","unresolved":false,"context_lines":[{"line_number":107,"context_line":"Alternatives"},{"line_number":108,"context_line":"------------"},{"line_number":109,"context_line":""},{"line_number":110,"context_line":"Continue with shadow mapping [2] as the only option for providing federated"},{"line_number":111,"context_line":"user provisioning; perhaps by providing rollback tooling or by limiting the"},{"line_number":112,"context_line":"authorization scope."},{"line_number":113,"context_line":""}],"source_content_type":"text/x-rst","patch_set":12,"id":"5a74a57a_691156af","line":110,"updated":"2016-11-30 15:59:43.000000000","message":"TBH I like this better than shadow mapping.","commit_id":"1fdc359491986a6199799a3c2f29074312dceff7"},{"author":{"_account_id":2218,"name":"Adam Young","email":"adam@younglogic.com","username":"ayoung"},"change_message_id":"bd59ff860691cd301677060f303edbc808585268","unresolved":false,"context_lines":[{"line_number":45,"context_line":"            \"domain_id\": \"1789d1\","},{"line_number":46,"context_line":"            \"enabled\": true,"},{"line_number":47,"context_line":"            \"name\": \"James Doe\","},{"line_number":48,"context_line":"            \"federated\": ["},{"line_number":49,"context_line":"                {"},{"line_number":50,"context_line":"                    \"idp_id\": \"1789d1\","},{"line_number":51,"context_line":"                    \"protocol_id\": saml2,"}],"source_content_type":"text/x-rst","patch_set":16,"id":"5a74a57a_543fb724","line":48,"updated":"2016-12-01 04:47:24.000000000","message":"Group these by IdP","commit_id":"a703415fcd82fd9aec5570d8f9226a024912979f"},{"author":{"_account_id":18338,"name":"Ron De Rose","email":"ronald.de.rose@intel.com","username":"derosenet"},"change_message_id":"994367c7e025868471a7bb3b070f8c41d11eee87","unresolved":false,"context_lines":[{"line_number":45,"context_line":"            \"domain_id\": \"1789d1\","},{"line_number":46,"context_line":"            \"enabled\": true,"},{"line_number":47,"context_line":"            \"name\": \"James Doe\","},{"line_number":48,"context_line":"            \"federated\": ["},{"line_number":49,"context_line":"                {"},{"line_number":50,"context_line":"                    \"idp_id\": \"1789d1\","},{"line_number":51,"context_line":"                    \"protocol_id\": saml2,"}],"source_content_type":"text/x-rst","patch_set":16,"id":"3a71b18c_f25d6bed","line":48,"in_reply_to":"5a74a57a_543fb724","updated":"2016-12-01 16:45:45.000000000","message":"Changed this to allow multiple protocols. Forgot this, thanks.","commit_id":"a703415fcd82fd9aec5570d8f9226a024912979f"},{"author":{"_account_id":2218,"name":"Adam Young","email":"adam@younglogic.com","username":"ayoung"},"change_message_id":"bd59ff860691cd301677060f303edbc808585268","unresolved":false,"context_lines":[{"line_number":49,"context_line":"                {"},{"line_number":50,"context_line":"                    \"idp_id\": \"1789d1\","},{"line_number":51,"context_line":"                    \"protocol_id\": saml2,"},{"line_number":52,"context_line":"                    \"unique_id\": \"jdoe\","},{"line_number":53,"context_line":"                    \"display_name\": \"James Doe\""},{"line_number":54,"context_line":"                }"},{"line_number":55,"context_line":"            ]"}],"source_content_type":"text/x-rst","patch_set":16,"id":"5a74a57a_742113fc","line":52,"updated":"2016-12-01 04:47:24.000000000","message":"These should be the prejmapped variable, not \"unique_id\" as that is not going to tell people if it came from REMOTE_USER or DN or whichever.  So much less usefull.","commit_id":"a703415fcd82fd9aec5570d8f9226a024912979f"},{"author":{"_account_id":18338,"name":"Ron De Rose","email":"ronald.de.rose@intel.com","username":"derosenet"},"change_message_id":"994367c7e025868471a7bb3b070f8c41d11eee87","unresolved":false,"context_lines":[{"line_number":49,"context_line":"                {"},{"line_number":50,"context_line":"                    \"idp_id\": \"1789d1\","},{"line_number":51,"context_line":"                    \"protocol_id\": saml2,"},{"line_number":52,"context_line":"                    \"unique_id\": \"jdoe\","},{"line_number":53,"context_line":"                    \"display_name\": \"James Doe\""},{"line_number":54,"context_line":"                }"},{"line_number":55,"context_line":"            ]"}],"source_content_type":"text/x-rst","patch_set":16,"id":"3a71b18c_d2aa2f70","line":52,"in_reply_to":"5a74a57a_742113fc","updated":"2016-12-01 16:45:45.000000000","message":"unique_id is what we are currently storing in the table; intended to be the dn, but doesn\u0027t have to be. Could be the user\u0027s email for example. And the unique_id and display name should be the same regardless of protocol.  I\u0027m not sure how remote_user fits in here.","commit_id":"a703415fcd82fd9aec5570d8f9226a024912979f"},{"author":{"_account_id":2218,"name":"Adam Young","email":"adam@younglogic.com","username":"ayoung"},"change_message_id":"bd59ff860691cd301677060f303edbc808585268","unresolved":false,"context_lines":[{"line_number":79,"context_line":"            ]"},{"line_number":80,"context_line":"        }"},{"line_number":81,"context_line":"    }"},{"line_number":82,"context_line":""},{"line_number":83,"context_line":"Creating a federated object for an existing user:"},{"line_number":84,"context_line":""},{"line_number":85,"context_line":".. code:: javascript"}],"source_content_type":"text/x-rst","patch_set":16,"id":"5a74a57a_74fd933a","line":82,"updated":"2016-12-01 04:47:24.000000000","message":"\"federated\": [\n                {\n                  \"idp_id\": \"1789d1\",\n                  protocols:[{\n                    \"protocol_id\": \"saml2\",\n                    \"DN\": \"jdoe\",\n                  },\n                  {\n                    \"protocol_id\": \u0027kerberos\u0027,\n                    \"REMOTE_USER\": \"jdoe\",\n                  },\n                  {\n                    \"protocol_id\": \u0027x509\u0027,\n                    \"SSL_CLIENT_S_DN\": \"jdoe\",\n                  }\n                  },                {\n                  \"idp_id\": \"fe0002\",\n                  protocols:[{\n                    \"protocol_id\": \"saml2\",\n                    \"DN\": \"johndoe\",\n                  },\n                  {\n                    \"protocol_id\": \u0027kerberos\u0027,\n                    \"REMOTE_USER\": \"juan dio\",\n                  },\n                  {\n                    \"protocol_id\": \u0027oidc\u0027,\n                    \"REMOTE_USER\": \"Chondough\",\n                  }\n                },","commit_id":"a703415fcd82fd9aec5570d8f9226a024912979f"},{"author":{"_account_id":18338,"name":"Ron De Rose","email":"ronald.de.rose@intel.com","username":"derosenet"},"change_message_id":"994367c7e025868471a7bb3b070f8c41d11eee87","unresolved":false,"context_lines":[{"line_number":79,"context_line":"            ]"},{"line_number":80,"context_line":"        }"},{"line_number":81,"context_line":"    }"},{"line_number":82,"context_line":""},{"line_number":83,"context_line":"Creating a federated object for an existing user:"},{"line_number":84,"context_line":""},{"line_number":85,"context_line":".. code:: javascript"}],"source_content_type":"text/x-rst","patch_set":16,"id":"3a71b18c_b2aa1318","line":82,"in_reply_to":"5a74a57a_74fd933a","updated":"2016-12-01 16:45:45.000000000","message":"I\u0027ve changed this to support multiple protocols. I would expect the unique_id (DN, SSL_CLIENT_S_DN...) to be the same regardless of protocol. And again, I\u0027m sure how remote_user fits in here with federation. Will try to ping you on IRC regarding this.","commit_id":"a703415fcd82fd9aec5570d8f9226a024912979f"},{"author":{"_account_id":2218,"name":"Adam Young","email":"adam@younglogic.com","username":"ayoung"},"change_message_id":"5f8d1d37e801373e2ec3507a646e88a656d45e62","unresolved":false,"context_lines":[{"line_number":89,"context_line":"        \"federated\": {"},{"line_number":90,"context_line":"            \"idp_id\": \"1789d1\","},{"line_number":91,"context_line":"            \"protocols\": [\"saml2\"],"},{"line_number":92,"context_line":"            \"unique_id\": \"jdoe\","},{"line_number":93,"context_line":"            \"display_name\": \"James Doe\""},{"line_number":94,"context_line":"        }"},{"line_number":95,"context_line":"    }"}],"source_content_type":"text/x-rst","patch_set":17,"id":"3a71b18c_4ed59041","line":92,"updated":"2016-12-01 21:16:36.000000000","message":"IF these two values are not per protocol or IDP, then move them up out of this section.  But the unique ID for a user is not guaranteed t obe the same between protocols.  for example  ayoung@REDHAT.COM for Kerberos and cn\u003dayoung,ou\u003dredhat.ouu.com from X509.\n\nIt is less important that the fields be named that way than that we have a way to distinguish between multiple protocols.\n\nThis might be a shortcoming of the current data model.","commit_id":"ff2471791d5a707f70113591c6cd78a53fff77e6"},{"author":{"_account_id":18338,"name":"Ron De Rose","email":"ronald.de.rose@intel.com","username":"derosenet"},"change_message_id":"5148b491e394e3cd35773422377c12fc008941f2","unresolved":false,"context_lines":[{"line_number":89,"context_line":"        \"federated\": {"},{"line_number":90,"context_line":"            \"idp_id\": \"1789d1\","},{"line_number":91,"context_line":"            \"protocols\": [\"saml2\"],"},{"line_number":92,"context_line":"            \"unique_id\": \"jdoe\","},{"line_number":93,"context_line":"            \"display_name\": \"James Doe\""},{"line_number":94,"context_line":"        }"},{"line_number":95,"context_line":"    }"}],"source_content_type":"text/x-rst","patch_set":17,"id":"3a71b18c_8d608b37","line":92,"in_reply_to":"3a71b18c_4ed59041","updated":"2016-12-01 23:28:03.000000000","message":"The current data model should still work. I\u0027ll update the spec, so that the unique_id is within the protocols object. Appreciate you feedback.","commit_id":"ff2471791d5a707f70113591c6cd78a53fff77e6"},{"author":{"_account_id":17860,"name":"Samuel de Medeiros Queiroz","email":"samueldmq@gmail.com","username":"samueldmq"},"change_message_id":"fe6be760e37c86537c1082d2b24b7d4354900c4e","unresolved":false,"context_lines":[{"line_number":11,"context_line":"`bp support-federated-attr \u003chttps://blueprints.launchpad.net/keystone/+spec/support-federated-attr\u003e`_"},{"line_number":12,"context_line":""},{"line_number":13,"context_line":"Extend the user API to support federated attributes so that we treat federated"},{"line_number":14,"context_line":"users like any other Keystone user."},{"line_number":15,"context_line":""},{"line_number":16,"context_line":"Problem Description"},{"line_number":17,"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":18,"id":"3a71b18c_1d38b33c","line":14,"range":{"start_line":14,"start_character":21,"end_line":14,"end_character":29},"updated":"2016-12-05 18:40:34.000000000","message":"(nit) keystone (occurs throughout the document)","commit_id":"e6357fdc3d64e0009bec886805af98d56205b0c8"},{"author":{"_account_id":17860,"name":"Samuel de Medeiros Queiroz","email":"samueldmq@gmail.com","username":"samueldmq"},"change_message_id":"fe6be760e37c86537c1082d2b24b7d4354900c4e","unresolved":false,"context_lines":[{"line_number":28,"context_line":"to federated users, since a federated user does not exist in Keystone until"},{"line_number":29,"context_line":"they authenticate for the first time. In addition, at the Barcelona Summit, we"},{"line_number":30,"context_line":"discussed a need for operators to be able to easily change and rollback"},{"line_number":31,"context_line":"provisioning."},{"line_number":32,"context_line":""},{"line_number":33,"context_line":"Proposed Change"},{"line_number":34,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"}],"source_content_type":"text/x-rst","patch_set":18,"id":"3a71b18c_fdadb784","line":31,"updated":"2016-12-05 18:40:34.000000000","message":"or even do de-provisioning","commit_id":"e6357fdc3d64e0009bec886805af98d56205b0c8"},{"author":{"_account_id":17860,"name":"Samuel de Medeiros Queiroz","email":"samueldmq@gmail.com","username":"samueldmq"},"change_message_id":"fe6be760e37c86537c1082d2b24b7d4354900c4e","unresolved":false,"context_lines":[{"line_number":127,"context_line":""},{"line_number":128,"context_line":".. code:: javascript"},{"line_number":129,"context_line":""},{"line_number":130,"context_line":"    GET /v3/users/?unique_id\u003d{unique_id}"},{"line_number":131,"context_line":""},{"line_number":132,"context_line":"If the unique_id was not unique across the organization, the request would need"},{"line_number":133,"context_line":"to include additional parameters in order to return the specific user."}],"source_content_type":"text/x-rst","patch_set":18,"id":"3a71b18c_7d7527f8","line":130,"range":{"start_line":130,"start_character":19,"end_line":130,"end_character":40},"updated":"2016-12-05 18:40:34.000000000","message":"Could be more specific: ?federated.protocols.unique_id\u003d{unique_id}\n\nHowever this is implementation detail, the concept is fine.","commit_id":"e6357fdc3d64e0009bec886805af98d56205b0c8"}]}
