)]}'
{"/COMMIT_MSG":[{"author":{"_account_id":4,"name":"Dolph Mathews","email":"dolph.mathews@gmail.com","username":"dolph"},"change_message_id":"adb96b19b304c05bc2d8aec887af24730df5da58","unresolved":false,"context_lines":[{"line_number":4,"context_line":"Commit:     Steve Martinelli \u003cstevemar@ca.ibm.com\u003e"},{"line_number":5,"context_line":"CommitDate: 2014-06-15 01:10:30 -0400"},{"line_number":6,"context_line":""},{"line_number":7,"context_line":"Implements: blueprint keystone-to-keystone-federation"},{"line_number":8,"context_line":""},{"line_number":9,"context_line":"Initial draft of the specification for keystone to keystone federation"},{"line_number":10,"context_line":""}],"source_content_type":"text/x-gerrit-commit-message","patch_set":3,"id":"1ae5cdf2_95062f84","line":7,"updated":"2014-06-17 14:09:41.000000000","message":"this isn\u0027t actually implementing anything; write a one line summary, not a bp reference","commit_id":"fe33d5591ac2c1c2cae9b2c0f86f6912cfd85977"},{"author":{"_account_id":4,"name":"Dolph Mathews","email":"dolph.mathews@gmail.com","username":"dolph"},"change_message_id":"adb96b19b304c05bc2d8aec887af24730df5da58","unresolved":false,"context_lines":[{"line_number":6,"context_line":""},{"line_number":7,"context_line":"Implements: blueprint keystone-to-keystone-federation"},{"line_number":8,"context_line":""},{"line_number":9,"context_line":"Initial draft of the specification for keystone to keystone federation"},{"line_number":10,"context_line":""},{"line_number":11,"context_line":"Co-Authored-By: Steve Martinelli \u003cstevemar@ca.ibm.com\u003e"},{"line_number":12,"context_line":"Change-Id: I648e6a9a18936c28c5104ae56c1127ac980be5e3"}],"source_content_type":"text/x-gerrit-commit-message","patch_set":3,"id":"1ae5cdf2_351f1bb9","line":9,"updated":"2014-06-17 14:09:41.000000000","message":"propose it as if it\u0027s the final copy; we\u0027re not going to approve an \"initial draft\"","commit_id":"fe33d5591ac2c1c2cae9b2c0f86f6912cfd85977"}],"specs/juno/keystone-to-keystone-federation.rst":[{"author":{"_account_id":1916,"name":"Guang Yee","email":"gyee@suse.com","username":"guang-yee"},"change_message_id":"b4ec678e7dca2cef7535beb309cb7b0bae253d9f","unresolved":false,"context_lines":[{"line_number":44,"context_line":""},{"line_number":45,"context_line":"**Use case 1: Workload management:**"},{"line_number":46,"context_line":""},{"line_number":47,"context_line":"CERN has one OpenStack cloud set-up (\"internal cloud\") within their data"},{"line_number":48,"context_line":"center. They have Keystone sitting on top of an LDAP instance. They would"},{"line_number":49,"context_line":"like to allocate cloud workload between multiple public cloud service"},{"line_number":50,"context_line":"providers (\"CSP\"), should their internal cloud not have enough bandwidth"}],"source_content_type":"text/x-rst","patch_set":3,"id":"1ae5cdf2_336ca508","line":47,"updated":"2014-06-17 07:06:25.000000000","message":"Not sure if we want to invent a new term \"internal cloud\" here. This is basically trust between two independently-operated clouds","commit_id":"fe33d5591ac2c1c2cae9b2c0f86f6912cfd85977"},{"author":{"_account_id":6482,"name":"Steve Martinelli","email":"s.martinelli@gmail.com","username":"stevemar"},"change_message_id":"5b4688c9387d6f95e13b7c353c3c503357b21813","unresolved":false,"context_lines":[{"line_number":44,"context_line":""},{"line_number":45,"context_line":"**Use case 1: Workload management:**"},{"line_number":46,"context_line":""},{"line_number":47,"context_line":"CERN has one OpenStack cloud set-up (\"internal cloud\") within their data"},{"line_number":48,"context_line":"center. They have Keystone sitting on top of an LDAP instance. They would"},{"line_number":49,"context_line":"like to allocate cloud workload between multiple public cloud service"},{"line_number":50,"context_line":"providers (\"CSP\"), should their internal cloud not have enough bandwidth"}],"source_content_type":"text/x-rst","patch_set":3,"id":"1ae5cdf2_5f622fda","line":47,"in_reply_to":"1ae5cdf2_336ca508","updated":"2014-06-23 20:31:21.000000000","message":"done - removed the term internal cloud","commit_id":"fe33d5591ac2c1c2cae9b2c0f86f6912cfd85977"},{"author":{"_account_id":5707,"name":"Henry Nash","email":"henryn@linux.vnet.ibm.com","username":"henry-nash"},"change_message_id":"4002b14d92554ddbc881772dff4fca03bda8d78b","unresolved":false,"context_lines":[{"line_number":64,"context_line":"up on Black Friday, but do not have the infrastructure in place to handle"},{"line_number":65,"context_line":"the projected traffic. They are even unsure of what the projected traffic"},{"line_number":66,"context_line":"could be. They would like to auto-scale their application across CSPs."},{"line_number":67,"context_line":""},{"line_number":68,"context_line":""},{"line_number":69,"context_line":"Proposed Change"},{"line_number":70,"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":3,"id":"1ae5cdf2_2b45fc14","line":67,"updated":"2014-06-17 14:46:15.000000000","message":"I\u0027d suggest there is a third (and easier) use case - that of an enterprise wanting to federate between multiple in-house openstack installations - e.g. they have one in each data centre, common internal IdP, but separately managed assignments in each.","commit_id":"fe33d5591ac2c1c2cae9b2c0f86f6912cfd85977"},{"author":{"_account_id":6482,"name":"Steve Martinelli","email":"s.martinelli@gmail.com","username":"stevemar"},"change_message_id":"5b4688c9387d6f95e13b7c353c3c503357b21813","unresolved":false,"context_lines":[{"line_number":64,"context_line":"up on Black Friday, but do not have the infrastructure in place to handle"},{"line_number":65,"context_line":"the projected traffic. They are even unsure of what the projected traffic"},{"line_number":66,"context_line":"could be. They would like to auto-scale their application across CSPs."},{"line_number":67,"context_line":""},{"line_number":68,"context_line":""},{"line_number":69,"context_line":"Proposed Change"},{"line_number":70,"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":3,"id":"1ae5cdf2_9fb3d74c","line":67,"in_reply_to":"1ae5cdf2_2b45fc14","updated":"2014-06-23 20:31:21.000000000","message":"OK - adding 3rd use case:\n\n**Use case 3: Multiple in-house OpenStack implementations:**\n\nACME has several OpenStack clouds setup, and each one maintains its own set of assignments. They would like to enable identity federation\tacross their multiple clouds so that an identity accessing each cloud doesn\u0027t need to maintain several tokens and credentials.","commit_id":"fe33d5591ac2c1c2cae9b2c0f86f6912cfd85977"},{"author":{"_account_id":1916,"name":"Guang Yee","email":"gyee@suse.com","username":"guang-yee"},"change_message_id":"b4ec678e7dca2cef7535beb309cb7b0bae253d9f","unresolved":false,"context_lines":[{"line_number":82,"context_line":"two way trust between \"ACME\" and \"BETA\", \"ACME\" would need to set-up \"BETA\""},{"line_number":83,"context_line":"as a trusted service provider and a trusted identity provider. \"BETA\" would"},{"line_number":84,"context_line":"have to set-up \"ACME\" as a trusted service provider and a trusted identity"},{"line_number":85,"context_line":"provider as well."},{"line_number":86,"context_line":""},{"line_number":87,"context_line":"To keep things simple, we should only consider one trust relationship at a"},{"line_number":88,"context_line":"time (since trust is not commutative, nor bi-directional). So to establish"}],"source_content_type":"text/x-rst","patch_set":3,"id":"1ae5cdf2_93cc9963","line":85,"updated":"2014-06-17 07:06:25.000000000","message":"Is two way trust is mandatory or just an example here?","commit_id":"fe33d5591ac2c1c2cae9b2c0f86f6912cfd85977"},{"author":{"_account_id":8978,"name":"Marek Denis","email":"marek.denis+openstack@gmail.com","username":"marek-denis"},"change_message_id":"6db17fac9597f79784d9e2a7fabb9c9c6304b9d0","unresolved":false,"context_lines":[{"line_number":82,"context_line":"two way trust between \"ACME\" and \"BETA\", \"ACME\" would need to set-up \"BETA\""},{"line_number":83,"context_line":"as a trusted service provider and a trusted identity provider. \"BETA\" would"},{"line_number":84,"context_line":"have to set-up \"ACME\" as a trusted service provider and a trusted identity"},{"line_number":85,"context_line":"provider as well."},{"line_number":86,"context_line":""},{"line_number":87,"context_line":"To keep things simple, we should only consider one trust relationship at a"},{"line_number":88,"context_line":"time (since trust is not commutative, nor bi-directional). So to establish"}],"source_content_type":"text/x-rst","patch_set":3,"id":"1ae5cdf2_c45d7917","line":85,"in_reply_to":"1ae5cdf2_93cc9963","updated":"2014-06-17 08:26:58.000000000","message":"I think an example here, especially after looking at the paragraph below.  At least in my opinion it should be enough to configure CloudA trust CloudB as IdP, and CloudB trust CloudA as SP and due to that configuration users from CloudB can burst into CloudA, not the other way round, which is often a desired situation (see the CERN/Rackspace example below).","commit_id":"fe33d5591ac2c1c2cae9b2c0f86f6912cfd85977"},{"author":{"_account_id":6482,"name":"Steve Martinelli","email":"s.martinelli@gmail.com","username":"stevemar"},"change_message_id":"5b4688c9387d6f95e13b7c353c3c503357b21813","unresolved":false,"context_lines":[{"line_number":82,"context_line":"two way trust between \"ACME\" and \"BETA\", \"ACME\" would need to set-up \"BETA\""},{"line_number":83,"context_line":"as a trusted service provider and a trusted identity provider. \"BETA\" would"},{"line_number":84,"context_line":"have to set-up \"ACME\" as a trusted service provider and a trusted identity"},{"line_number":85,"context_line":"provider as well."},{"line_number":86,"context_line":""},{"line_number":87,"context_line":"To keep things simple, we should only consider one trust relationship at a"},{"line_number":88,"context_line":"time (since trust is not commutative, nor bi-directional). So to establish"}],"source_content_type":"text/x-rst","patch_set":3,"id":"1ae5cdf2_1ff6e7f9","line":85,"in_reply_to":"1ae5cdf2_c45d7917","updated":"2014-06-23 20:31:21.000000000","message":"Marek is correct, it\u0027s not mandatory, it\u0027s just an example here","commit_id":"fe33d5591ac2c1c2cae9b2c0f86f6912cfd85977"},{"author":{"_account_id":1916,"name":"Guang Yee","email":"gyee@suse.com","username":"guang-yee"},"change_message_id":"b4ec678e7dca2cef7535beb309cb7b0bae253d9f","unresolved":false,"context_lines":[{"line_number":90,"context_line":"trusted identity provider. (BETA can do likewise if it wants to, but this is"},{"line_number":91,"context_line":"a separate trust relationship so lets ignore it for now). Now whenever ACME"},{"line_number":92,"context_line":"gets a digitally signed identity token issued by BETA it can validate it."},{"line_number":93,"context_line":"However, if BETA issues symmetrically encrypted tokens or similar, then BETA"},{"line_number":94,"context_line":"needs to trust ACME to validate its tokens. If BETA knows that it is safe to"},{"line_number":95,"context_line":"release identity attributes to ACME, BETA needs to add a one way trust"},{"line_number":96,"context_line":"relationship saying that ACME is entitled to receive its tokens. For a"}],"source_content_type":"text/x-rst","patch_set":3,"id":"1ae5cdf2_535e9177","line":93,"updated":"2014-06-17 07:06:25.000000000","message":"\"symmetrically encrypted\"? We don\u0027t do that in Keystone do we?","commit_id":"fe33d5591ac2c1c2cae9b2c0f86f6912cfd85977"},{"author":{"_account_id":1916,"name":"Guang Yee","email":"gyee@suse.com","username":"guang-yee"},"change_message_id":"b4ec678e7dca2cef7535beb309cb7b0bae253d9f","unresolved":false,"context_lines":[{"line_number":91,"context_line":"a separate trust relationship so lets ignore it for now). Now whenever ACME"},{"line_number":92,"context_line":"gets a digitally signed identity token issued by BETA it can validate it."},{"line_number":93,"context_line":"However, if BETA issues symmetrically encrypted tokens or similar, then BETA"},{"line_number":94,"context_line":"needs to trust ACME to validate its tokens. If BETA knows that it is safe to"},{"line_number":95,"context_line":"release identity attributes to ACME, BETA needs to add a one way trust"},{"line_number":96,"context_line":"relationship saying that ACME is entitled to receive its tokens. For a"},{"line_number":97,"context_line":"real-life example, CERN might want to buy some resources from Rackspace,"}],"source_content_type":"text/x-rst","patch_set":3,"id":"1ae5cdf2_33e745ae","line":94,"updated":"2014-06-17 07:06:25.000000000","message":"This sentence doesn\u0027t seem right. It should be the other way around, the validator trust the issuer.","commit_id":"fe33d5591ac2c1c2cae9b2c0f86f6912cfd85977"},{"author":{"_account_id":1916,"name":"Guang Yee","email":"gyee@suse.com","username":"guang-yee"},"change_message_id":"b4ec678e7dca2cef7535beb309cb7b0bae253d9f","unresolved":false,"context_lines":[{"line_number":94,"context_line":"needs to trust ACME to validate its tokens. If BETA knows that it is safe to"},{"line_number":95,"context_line":"release identity attributes to ACME, BETA needs to add a one way trust"},{"line_number":96,"context_line":"relationship saying that ACME is entitled to receive its tokens. For a"},{"line_number":97,"context_line":"real-life example, CERN might want to buy some resources from Rackspace,"},{"line_number":98,"context_line":"whereas CERN doesn\u0027t want Rackspace to use their resources. Of course, the"},{"line_number":99,"context_line":"reciprocal trust arrangements can be made between ACME and BETA, but this"},{"line_number":100,"context_line":"should be considered to be a repeat of the above, only in the opposite"}],"source_content_type":"text/x-rst","patch_set":3,"id":"1ae5cdf2_33d025c9","line":97,"updated":"2014-06-17 07:06:25.000000000","message":"Can we stick to ACME and BETA instead of CERN and Rackspace? :) Don\u0027t think we want to open up the flood gate here.","commit_id":"fe33d5591ac2c1c2cae9b2c0f86f6912cfd85977"},{"author":{"_account_id":6482,"name":"Steve Martinelli","email":"s.martinelli@gmail.com","username":"stevemar"},"change_message_id":"5b4688c9387d6f95e13b7c353c3c503357b21813","unresolved":false,"context_lines":[{"line_number":94,"context_line":"needs to trust ACME to validate its tokens. If BETA knows that it is safe to"},{"line_number":95,"context_line":"release identity attributes to ACME, BETA needs to add a one way trust"},{"line_number":96,"context_line":"relationship saying that ACME is entitled to receive its tokens. For a"},{"line_number":97,"context_line":"real-life example, CERN might want to buy some resources from Rackspace,"},{"line_number":98,"context_line":"whereas CERN doesn\u0027t want Rackspace to use their resources. Of course, the"},{"line_number":99,"context_line":"reciprocal trust arrangements can be made between ACME and BETA, but this"},{"line_number":100,"context_line":"should be considered to be a repeat of the above, only in the opposite"}],"source_content_type":"text/x-rst","patch_set":3,"id":"1ae5cdf2_9f6677ba","line":97,"in_reply_to":"1ae5cdf2_33d025c9","updated":"2014-06-23 20:31:21.000000000","message":"Done - switched to acme and beta","commit_id":"fe33d5591ac2c1c2cae9b2c0f86f6912cfd85977"},{"author":{"_account_id":8978,"name":"Marek Denis","email":"marek.denis+openstack@gmail.com","username":"marek-denis"},"change_message_id":"6c0b8612308d7b24d47f02c0e29754d392ca0cf4","unresolved":false,"context_lines":[{"line_number":105,"context_line":"offer so that it could build adequate token scope across multiple OpenStack"},{"line_number":106,"context_line":"clouds. This can be done in a variety of ways. One idea is to have a feed"},{"line_number":107,"context_line":"provided by Keystone that indicates what services and endpoints are accessible"},{"line_number":108,"context_line":"to authenticated identities."},{"line_number":109,"context_line":""},{"line_number":110,"context_line":"3. The Keystone acting as a trusted service provider will get many tokens"},{"line_number":111,"context_line":"that are not within it\u0027s local store. It will need to be able to decipher"}],"source_content_type":"text/x-rst","patch_set":3,"id":"1ae5cdf2_f8e168fd","line":108,"updated":"2014-06-16 10:13:14.000000000","message":"This paragraph confuses me a little bit. When saying \"..feed provided by Keystone that indicates...\" are you depicting a client library pooling its\u0027 local Keystone for federated service catalog, or local Keystone pooling other Keystones to update the list of remote services and endpoints, so that list can be later squeezed into token?","commit_id":"fe33d5591ac2c1c2cae9b2c0f86f6912cfd85977"},{"author":{"_account_id":6482,"name":"Steve Martinelli","email":"s.martinelli@gmail.com","username":"stevemar"},"change_message_id":"5b4688c9387d6f95e13b7c353c3c503357b21813","unresolved":false,"context_lines":[{"line_number":105,"context_line":"offer so that it could build adequate token scope across multiple OpenStack"},{"line_number":106,"context_line":"clouds. This can be done in a variety of ways. One idea is to have a feed"},{"line_number":107,"context_line":"provided by Keystone that indicates what services and endpoints are accessible"},{"line_number":108,"context_line":"to authenticated identities."},{"line_number":109,"context_line":""},{"line_number":110,"context_line":"3. The Keystone acting as a trusted service provider will get many tokens"},{"line_number":111,"context_line":"that are not within it\u0027s local store. It will need to be able to decipher"}],"source_content_type":"text/x-rst","patch_set":3,"id":"1ae5cdf2_5f1a2f19","line":108,"in_reply_to":"1ae5cdf2_9359f95d","updated":"2014-06-23 20:31:21.000000000","message":"changed the wording here","commit_id":"fe33d5591ac2c1c2cae9b2c0f86f6912cfd85977"},{"author":{"_account_id":1916,"name":"Guang Yee","email":"gyee@suse.com","username":"guang-yee"},"change_message_id":"b4ec678e7dca2cef7535beb309cb7b0bae253d9f","unresolved":false,"context_lines":[{"line_number":105,"context_line":"offer so that it could build adequate token scope across multiple OpenStack"},{"line_number":106,"context_line":"clouds. This can be done in a variety of ways. One idea is to have a feed"},{"line_number":107,"context_line":"provided by Keystone that indicates what services and endpoints are accessible"},{"line_number":108,"context_line":"to authenticated identities."},{"line_number":109,"context_line":""},{"line_number":110,"context_line":"3. The Keystone acting as a trusted service provider will get many tokens"},{"line_number":111,"context_line":"that are not within it\u0027s local store. It will need to be able to decipher"}],"source_content_type":"text/x-rst","patch_set":3,"id":"1ae5cdf2_9359f95d","line":108,"in_reply_to":"1ae5cdf2_f8e168fd","updated":"2014-06-17 07:06:25.000000000","message":"Same here. There should be a easier way to say trusted endpoints.","commit_id":"fe33d5591ac2c1c2cae9b2c0f86f6912cfd85977"},{"author":{"_account_id":1916,"name":"Guang Yee","email":"gyee@suse.com","username":"guang-yee"},"change_message_id":"b4ec678e7dca2cef7535beb309cb7b0bae253d9f","unresolved":false,"context_lines":[{"line_number":112,"context_line":"what the originating Keystone is from the token in order to:"},{"line_number":113,"context_line":""},{"line_number":114,"context_line":"  1. Validate that the originating Keystone is listed as a trusted identity"},{"line_number":115,"context_line":"  provider."},{"line_number":116,"context_line":""},{"line_number":117,"context_line":"  2. And if so, initiate the federation handshake with that originating"},{"line_number":118,"context_line":"  Keystone to validate the token and create an ephemeral identity locally."}],"source_content_type":"text/x-rst","patch_set":3,"id":"1ae5cdf2_53169156","line":115,"updated":"2014-06-17 07:06:25.000000000","message":"If we are using PKI tokens, the SignerInfo field in CMS should tell us where it is coming from.\n\nhttp://tools.ietf.org/html/rfc5652#section-5.3","commit_id":"fe33d5591ac2c1c2cae9b2c0f86f6912cfd85977"},{"author":{"_account_id":6482,"name":"Steve Martinelli","email":"s.martinelli@gmail.com","username":"stevemar"},"change_message_id":"5b4688c9387d6f95e13b7c353c3c503357b21813","unresolved":false,"context_lines":[{"line_number":112,"context_line":"what the originating Keystone is from the token in order to:"},{"line_number":113,"context_line":""},{"line_number":114,"context_line":"  1. Validate that the originating Keystone is listed as a trusted identity"},{"line_number":115,"context_line":"  provider."},{"line_number":116,"context_line":""},{"line_number":117,"context_line":"  2. And if so, initiate the federation handshake with that originating"},{"line_number":118,"context_line":"  Keystone to validate the token and create an ephemeral identity locally."}],"source_content_type":"text/x-rst","patch_set":3,"id":"1ae5cdf2_bfd0932c","line":115,"in_reply_to":"1ae5cdf2_53169156","updated":"2014-06-23 20:31:21.000000000","message":"Thanks! I added that part in","commit_id":"fe33d5591ac2c1c2cae9b2c0f86f6912cfd85977"},{"author":{"_account_id":6482,"name":"Steve Martinelli","email":"s.martinelli@gmail.com","username":"stevemar"},"change_message_id":"7b0bc69fa36772d098359aba7ffb2fdd52382bdd","unresolved":false,"context_lines":[{"line_number":115,"context_line":"  provider."},{"line_number":116,"context_line":""},{"line_number":117,"context_line":"  2. And if so, initiate the federation handshake with that originating"},{"line_number":118,"context_line":"  Keystone to validate the token and create an ephemeral identity locally."},{"line_number":119,"context_line":""},{"line_number":120,"context_line":"4. Should the end user revoke their token, or their token is revoked by"},{"line_number":121,"context_line":"other means including the deletion of the service provider trust, that needs"}],"source_content_type":"text/x-rst","patch_set":3,"id":"1ae5cdf2_d1aad96f","line":118,"updated":"2014-06-15 05:16:42.000000000","message":"So this raised a bit of a flag for me, I thought we were against creating ephemeral identities in Keystone.","commit_id":"fe33d5591ac2c1c2cae9b2c0f86f6912cfd85977"},{"author":{"_account_id":8978,"name":"Marek Denis","email":"marek.denis+openstack@gmail.com","username":"marek-denis"},"change_message_id":"6c0b8612308d7b24d47f02c0e29754d392ca0cf4","unresolved":false,"context_lines":[{"line_number":115,"context_line":"  provider."},{"line_number":116,"context_line":""},{"line_number":117,"context_line":"  2. And if so, initiate the federation handshake with that originating"},{"line_number":118,"context_line":"  Keystone to validate the token and create an ephemeral identity locally."},{"line_number":119,"context_line":""},{"line_number":120,"context_line":"4. Should the end user revoke their token, or their token is revoked by"},{"line_number":121,"context_line":"other means including the deletion of the service provider trust, that needs"}],"source_content_type":"text/x-rst","patch_set":3,"id":"1ae5cdf2_1a67ecb8","line":118,"in_reply_to":"1ae5cdf2_d1aad96f","updated":"2014-06-16 10:13:14.000000000","message":"I think by saying \u0027identity\u0027 Joe meant \u0027federated/ephemeral user\u0027 identified by an unscoped (and later scoped) token. Something we already create today and don\u0027t even store it anywhere.","commit_id":"fe33d5591ac2c1c2cae9b2c0f86f6912cfd85977"},{"author":{"_account_id":1916,"name":"Guang Yee","email":"gyee@suse.com","username":"guang-yee"},"change_message_id":"b4ec678e7dca2cef7535beb309cb7b0bae253d9f","unresolved":false,"context_lines":[{"line_number":120,"context_line":"4. Should the end user revoke their token, or their token is revoked by"},{"line_number":121,"context_line":"other means including the deletion of the service provider trust, that needs"},{"line_number":122,"context_line":"to be broadcast out by the originating Keystone to trusted service providers"},{"line_number":123,"context_line":"so that the revocation is all encompassing."},{"line_number":124,"context_line":""},{"line_number":125,"context_line":"Alternatives"},{"line_number":126,"context_line":"------------"}],"source_content_type":"text/x-rst","patch_set":3,"id":"1ae5cdf2_b3043519","line":123,"updated":"2014-06-17 07:06:25.000000000","message":"Yes, we can leverage the existing revocation events.","commit_id":"fe33d5591ac2c1c2cae9b2c0f86f6912cfd85977"},{"author":{"_account_id":6482,"name":"Steve Martinelli","email":"s.martinelli@gmail.com","username":"stevemar"},"change_message_id":"5b4688c9387d6f95e13b7c353c3c503357b21813","unresolved":false,"context_lines":[{"line_number":120,"context_line":"4. Should the end user revoke their token, or their token is revoked by"},{"line_number":121,"context_line":"other means including the deletion of the service provider trust, that needs"},{"line_number":122,"context_line":"to be broadcast out by the originating Keystone to trusted service providers"},{"line_number":123,"context_line":"so that the revocation is all encompassing."},{"line_number":124,"context_line":""},{"line_number":125,"context_line":"Alternatives"},{"line_number":126,"context_line":"------------"}],"source_content_type":"text/x-rst","patch_set":3,"id":"1ae5cdf2_9febd7db","line":123,"in_reply_to":"1ae5cdf2_b3043519","updated":"2014-06-23 20:31:21.000000000","message":"Added this in.","commit_id":"fe33d5591ac2c1c2cae9b2c0f86f6912cfd85977"},{"author":{"_account_id":8978,"name":"Marek Denis","email":"marek.denis+openstack@gmail.com","username":"marek-denis"},"change_message_id":"6db17fac9597f79784d9e2a7fabb9c9c6304b9d0","unresolved":false,"context_lines":[{"line_number":122,"context_line":"to be broadcast out by the originating Keystone to trusted service providers"},{"line_number":123,"context_line":"so that the revocation is all encompassing."},{"line_number":124,"context_line":""},{"line_number":125,"context_line":"Alternatives"},{"line_number":126,"context_line":"------------"},{"line_number":127,"context_line":""},{"line_number":128,"context_line":"One alternative is to ask the end user to manage multiple credentials, a set"}],"source_content_type":"text/x-rst","patch_set":3,"id":"1ae5cdf2_00f76dd5","line":125,"updated":"2014-06-17 08:26:58.000000000","message":"Hint: Another alternative could be quite similar - different token per cloud set-up, however obtained via federation authn (so, the same set of credentials).\nA client still uses the same set of credentials (from comapny\u0027s LDAP), but due to federation can access autonomic clouds. To make it work we would make a client very smart and of course handle many tokens at the moment. Not a perfect solution, but still better than different token per cloud managed with different set of credentials per cloud.","commit_id":"fe33d5591ac2c1c2cae9b2c0f86f6912cfd85977"},{"author":{"_account_id":1916,"name":"Guang Yee","email":"gyee@suse.com","username":"guang-yee"},"change_message_id":"b4ec678e7dca2cef7535beb309cb7b0bae253d9f","unresolved":false,"context_lines":[{"line_number":161,"context_line":"  Indicates whether the identity service (Keystone) should assert federation"},{"line_number":162,"context_line":"  identities to this service provider."},{"line_number":163,"context_line":""},{"line_number":164,"context_line":"Register an service provider: ``PUT /OS-FEDERATION/service_providers/{sp_id}``"},{"line_number":165,"context_line":""},{"line_number":166,"context_line":"Request::"},{"line_number":167,"context_line":""}],"source_content_type":"text/x-rst","patch_set":3,"id":"1ae5cdf2_4e2428af","line":164,"updated":"2014-06-17 07:06:25.000000000","message":"I don\u0027t understand why we need new API for this. We should be able to leverage the existing Federation framework. External Keystone is just another IdP.","commit_id":"fe33d5591ac2c1c2cae9b2c0f86f6912cfd85977"},{"author":{"_account_id":8978,"name":"Marek Denis","email":"marek.denis+openstack@gmail.com","username":"marek-denis"},"change_message_id":"6db17fac9597f79784d9e2a7fabb9c9c6304b9d0","unresolved":false,"context_lines":[{"line_number":161,"context_line":"  Indicates whether the identity service (Keystone) should assert federation"},{"line_number":162,"context_line":"  identities to this service provider."},{"line_number":163,"context_line":""},{"line_number":164,"context_line":"Register an service provider: ``PUT /OS-FEDERATION/service_providers/{sp_id}``"},{"line_number":165,"context_line":""},{"line_number":166,"context_line":"Request::"},{"line_number":167,"context_line":""}],"source_content_type":"text/x-rst","patch_set":3,"id":"1ae5cdf2_89fd4a3e","line":164,"in_reply_to":"1ae5cdf2_4e2428af","updated":"2014-06-17 08:26:58.000000000","message":"According to the spec the Keystone now becomes an Indentity Provider issuing assertions (SAML assertion, openId claims etc) to trusted Service Providers. In a standard federation world such IdP will issue an assertion only to a trusted SP, not to everybody who wants this. So this API is to setup a list of trusted SPs from a Keystone-Idp perspective.","commit_id":"fe33d5591ac2c1c2cae9b2c0f86f6912cfd85977"},{"author":{"_account_id":8978,"name":"Marek Denis","email":"marek.denis+openstack@gmail.com","username":"marek-denis"},"change_message_id":"6c0b8612308d7b24d47f02c0e29754d392ca0cf4","unresolved":false,"context_lines":[{"line_number":293,"context_line":"  Indicates which mapping should be used to process federated authentication"},{"line_number":294,"context_line":"  requests."},{"line_number":295,"context_line":""},{"line_number":296,"context_line":"**Mappings**: ``/OS-FEDERATION/mappings``"},{"line_number":297,"context_line":""},{"line_number":298,"context_line":"The same mapping CRUD defined in `icehouse federation mapping spec"},{"line_number":299,"context_line":"\u003chttps://github.com/openstack/identity-api/blob/master/v3/src/markdown/identity-api-v3-os-federation-ext.md#mappings-os-federationmappings\u003e`_"}],"source_content_type":"text/x-rst","patch_set":3,"id":"1ae5cdf2_b88600da","line":296,"updated":"2014-06-16 10:13:14.000000000","message":"I currently don\u0027t see any use for mappings on the Keystone-IdPs.\nWhat\u0027s the input for that mapping?","commit_id":"fe33d5591ac2c1c2cae9b2c0f86f6912cfd85977"},{"author":{"_account_id":7725,"name":"David Stanek","email":"dstanek@dstanek.com","username":"dstanek"},"change_message_id":"625bc24b8df76259aa2ee6ccc4479d5e2cbfe4ff","unresolved":false,"context_lines":[{"line_number":293,"context_line":"  Indicates which mapping should be used to process federated authentication"},{"line_number":294,"context_line":"  requests."},{"line_number":295,"context_line":""},{"line_number":296,"context_line":"**Mappings**: ``/OS-FEDERATION/mappings``"},{"line_number":297,"context_line":""},{"line_number":298,"context_line":"The same mapping CRUD defined in `icehouse federation mapping spec"},{"line_number":299,"context_line":"\u003chttps://github.com/openstack/identity-api/blob/master/v3/src/markdown/identity-api-v3-os-federation-ext.md#mappings-os-federationmappings\u003e`_"}],"source_content_type":"text/x-rst","patch_set":3,"id":"1ae5cdf2_ab2d8cff","line":296,"in_reply_to":"1ae5cdf2_a9fa0641","updated":"2014-06-17 14:54:41.000000000","message":"I\u0027m not sure about this. The mapping is used by Keystone on an incoming assertion to map remote data to the local Keystone schema. In the vendor example isn\u0027t this relationship reversed? Are you going to use the mapping to control what we send to the vendor? If so, how?","commit_id":"fe33d5591ac2c1c2cae9b2c0f86f6912cfd85977"},{"author":{"_account_id":1228,"name":"Joe Savak","email":"jsavak@gmail.com","username":"jsavak"},"change_message_id":"19b1737b30d56a19f12b8cfbf3cb3f3b192b06bb","unresolved":false,"context_lines":[{"line_number":293,"context_line":"  Indicates which mapping should be used to process federated authentication"},{"line_number":294,"context_line":"  requests."},{"line_number":295,"context_line":""},{"line_number":296,"context_line":"**Mappings**: ``/OS-FEDERATION/mappings``"},{"line_number":297,"context_line":""},{"line_number":298,"context_line":"The same mapping CRUD defined in `icehouse federation mapping spec"},{"line_number":299,"context_line":"\u003chttps://github.com/openstack/identity-api/blob/master/v3/src/markdown/identity-api-v3-os-federation-ext.md#mappings-os-federationmappings\u003e`_"}],"source_content_type":"text/x-rst","patch_set":3,"id":"1ae5cdf2_f9d400bf","line":296,"in_reply_to":"1ae5cdf2_b88600da","updated":"2014-06-16 21:09:27.000000000","message":"having a mapping tie in for service provider puts us in a better spot should the service we are integrating with not be openstack keystones. For example - the ticketing use case where i\u0027m using a vendor provided \"ticketing as a service\". I want to provide that ticketing api in the keystone service catalog (even though it isn\u0027t openstack). The ticketing system may require \"e-mail\" and \"f-lname\" as attrs but keystone knows that as \"email\" and \"username\"","commit_id":"fe33d5591ac2c1c2cae9b2c0f86f6912cfd85977"},{"author":{"_account_id":8978,"name":"Marek Denis","email":"marek.denis+openstack@gmail.com","username":"marek-denis"},"change_message_id":"6db17fac9597f79784d9e2a7fabb9c9c6304b9d0","unresolved":false,"context_lines":[{"line_number":293,"context_line":"  Indicates which mapping should be used to process federated authentication"},{"line_number":294,"context_line":"  requests."},{"line_number":295,"context_line":""},{"line_number":296,"context_line":"**Mappings**: ``/OS-FEDERATION/mappings``"},{"line_number":297,"context_line":""},{"line_number":298,"context_line":"The same mapping CRUD defined in `icehouse federation mapping spec"},{"line_number":299,"context_line":"\u003chttps://github.com/openstack/identity-api/blob/master/v3/src/markdown/identity-api-v3-os-federation-ext.md#mappings-os-federationmappings\u003e`_"}],"source_content_type":"text/x-rst","patch_set":3,"id":"1ae5cdf2_a9fa0641","line":296,"in_reply_to":"1ae5cdf2_f9d400bf","updated":"2014-06-17 08:26:58.000000000","message":"Ok, now I see it, you want to be in control how the assertion looks like :-)","commit_id":"fe33d5591ac2c1c2cae9b2c0f86f6912cfd85977"},{"author":{"_account_id":8978,"name":"Marek Denis","email":"marek.denis+openstack@gmail.com","username":"marek-denis"},"change_message_id":"6c0b8612308d7b24d47f02c0e29754d392ca0cf4","unresolved":false,"context_lines":[{"line_number":422,"context_line":"Other End User Impact"},{"line_number":423,"context_line":"---------------------"},{"line_number":424,"context_line":""},{"line_number":425,"context_line":"Potentially via ECP (https://wiki.shibboleth.net/confluence/display/SHIB2/ECP)"},{"line_number":426,"context_line":""},{"line_number":427,"context_line":"Performance Impact"},{"line_number":428,"context_line":"------------------"}],"source_content_type":"text/x-rst","patch_set":3,"id":"1ae5cdf2_18e374a5","line":425,"updated":"2014-06-16 10:13:14.000000000","message":"I think this might need some explanation. Is the client library somehow included in that workflow?","commit_id":"fe33d5591ac2c1c2cae9b2c0f86f6912cfd85977"},{"author":{"_account_id":6482,"name":"Steve Martinelli","email":"s.martinelli@gmail.com","username":"stevemar"},"change_message_id":"7b0bc69fa36772d098359aba7ffb2fdd52382bdd","unresolved":false,"context_lines":[{"line_number":461,"context_line":""},{"line_number":462,"context_line":"* Define a specification for adding and maintaining service providers."},{"line_number":463,"context_line":""},{"line_number":464,"context_line":"* Define and implement a publishing services the local Keystone has setup."},{"line_number":465,"context_line":"  (ex: \"nova\" at \"https://nova.acme.com\": TODO)"},{"line_number":466,"context_line":""},{"line_number":467,"context_line":"* Define and implement a method for listening to foreign Keystones"}],"source_content_type":"text/x-rst","patch_set":3,"id":"1ae5cdf2_31bbfdc4","line":464,"updated":"2014-06-15 05:16:42.000000000","message":"this needs to be fleshed out more","commit_id":"fe33d5591ac2c1c2cae9b2c0f86f6912cfd85977"},{"author":{"_account_id":6482,"name":"Steve Martinelli","email":"s.martinelli@gmail.com","username":"stevemar"},"change_message_id":"7b0bc69fa36772d098359aba7ffb2fdd52382bdd","unresolved":false,"context_lines":[{"line_number":464,"context_line":"* Define and implement a publishing services the local Keystone has setup."},{"line_number":465,"context_line":"  (ex: \"nova\" at \"https://nova.acme.com\": TODO)"},{"line_number":466,"context_line":""},{"line_number":467,"context_line":"* Define and implement a method for listening to foreign Keystones"},{"line_number":468,"context_line":"  (ex: beta-keystone supports \"swift\" at \"https://swift.beta.com\": TODO)"},{"line_number":469,"context_line":""},{"line_number":470,"context_line":"* Define and implement a method of validating foreign tokens: TODO"}],"source_content_type":"text/x-rst","patch_set":3,"id":"1ae5cdf2_11b8c1c6","line":467,"updated":"2014-06-15 05:16:42.000000000","message":"this needs to be fleshed out more","commit_id":"fe33d5591ac2c1c2cae9b2c0f86f6912cfd85977"},{"author":{"_account_id":5046,"name":"Lance Bragstad","email":"lbragstad@redhat.com","username":"ldbragst"},"change_message_id":"9e5a4b180151058b149481e0a71df7abe1095824","unresolved":false,"context_lines":[{"line_number":35,"context_line":"IdP and Keystone. This allowed Cloud Implementers to set-up single-sign-on"},{"line_number":36,"context_line":"when configuring their cloud and not incur the administrative overhead"},{"line_number":37,"context_line":"that comes with provisioning identities in Keystone. Keystone trusts the"},{"line_number":38,"context_line":"Identity provider enough to **accept federated identities from** them."},{"line_number":39,"context_line":"However, there is no way right now for one Keystone to trust another Keystone."},{"line_number":40,"context_line":"This is where one Keystone trusts another to **assert federation identities"},{"line_number":41,"context_line":"to** it."}],"source_content_type":"text/x-rst","patch_set":5,"id":"1ae5cdf2_c2b748f7","line":38,"updated":"2014-06-23 21:02:29.000000000","message":"Use IdP here?","commit_id":"611c844578e279455ba538cbe3220560cf41ca58"},{"author":{"_account_id":6482,"name":"Steve Martinelli","email":"s.martinelli@gmail.com","username":"stevemar"},"change_message_id":"e5cf88d1095b3554146d55f20a723d4c6c9a2035","unresolved":false,"context_lines":[{"line_number":35,"context_line":"IdP and Keystone. This allowed Cloud Implementers to set-up single-sign-on"},{"line_number":36,"context_line":"when configuring their cloud and not incur the administrative overhead"},{"line_number":37,"context_line":"that comes with provisioning identities in Keystone. Keystone trusts the"},{"line_number":38,"context_line":"Identity provider enough to **accept federated identities from** them."},{"line_number":39,"context_line":"However, there is no way right now for one Keystone to trust another Keystone."},{"line_number":40,"context_line":"This is where one Keystone trusts another to **assert federation identities"},{"line_number":41,"context_line":"to** it."}],"source_content_type":"text/x-rst","patch_set":5,"id":"1ae5cdf2_1ead0033","line":38,"in_reply_to":"1ae5cdf2_c2b748f7","updated":"2014-06-24 02:59:59.000000000","message":"Done","commit_id":"611c844578e279455ba538cbe3220560cf41ca58"},{"author":{"_account_id":5046,"name":"Lance Bragstad","email":"lbragstad@redhat.com","username":"ldbragst"},"change_message_id":"9e5a4b180151058b149481e0a71df7abe1095824","unresolved":false,"context_lines":[{"line_number":94,"context_line":"To keep things simple, we should only consider one trust relationship at a"},{"line_number":95,"context_line":"time (since trust is not commutative, nor bi-directional). So to establish"},{"line_number":96,"context_line":"one way trust between ACME and BETA, ACME would need to set up BETA as a"},{"line_number":97,"context_line":"trusted identity provider. (BETA can do likewise if it wants to, but this is"},{"line_number":98,"context_line":"a separate trust relationship so lets ignore it for now). Now whenever ACME"},{"line_number":99,"context_line":"gets a digitally signed identity token issued by BETA it can validate it."},{"line_number":100,"context_line":"However, if BETA issues symmetrically encrypted tokens or similar, then BETA"}],"source_content_type":"text/x-rst","patch_set":5,"id":"1ae5cdf2_42c7b846","line":97,"updated":"2014-06-23 21:02:29.000000000","message":"IdP?*","commit_id":"611c844578e279455ba538cbe3220560cf41ca58"},{"author":{"_account_id":6482,"name":"Steve Martinelli","email":"s.martinelli@gmail.com","username":"stevemar"},"change_message_id":"e5cf88d1095b3554146d55f20a723d4c6c9a2035","unresolved":false,"context_lines":[{"line_number":94,"context_line":"To keep things simple, we should only consider one trust relationship at a"},{"line_number":95,"context_line":"time (since trust is not commutative, nor bi-directional). So to establish"},{"line_number":96,"context_line":"one way trust between ACME and BETA, ACME would need to set up BETA as a"},{"line_number":97,"context_line":"trusted identity provider. (BETA can do likewise if it wants to, but this is"},{"line_number":98,"context_line":"a separate trust relationship so lets ignore it for now). Now whenever ACME"},{"line_number":99,"context_line":"gets a digitally signed identity token issued by BETA it can validate it."},{"line_number":100,"context_line":"However, if BETA issues symmetrically encrypted tokens or similar, then BETA"}],"source_content_type":"text/x-rst","patch_set":5,"id":"1ae5cdf2_be65ec1e","line":97,"in_reply_to":"1ae5cdf2_42c7b846","updated":"2014-06-24 02:59:59.000000000","message":"Done","commit_id":"611c844578e279455ba538cbe3220560cf41ca58"},{"author":{"_account_id":5046,"name":"Lance Bragstad","email":"lbragstad@redhat.com","username":"ldbragst"},"change_message_id":"9e5a4b180151058b149481e0a71df7abe1095824","unresolved":false,"context_lines":[{"line_number":107,"context_line":"should be considered to be a repeat of the above, only in the opposite"},{"line_number":108,"context_line":"direction."},{"line_number":109,"context_line":""},{"line_number":110,"context_line":"2. ACME\u0027s keystone mentioned in the above use cases above should"},{"line_number":111,"context_line":"have knowledge of what services and endpoints BETA offers so that"},{"line_number":112,"context_line":"it could build adequate token scope across both OpenStack clouds."},{"line_number":113,"context_line":"This can be done in a variety of ways. One idea is to allow ACME to"}],"source_content_type":"text/x-rst","patch_set":5,"id":"1ae5cdf2_c2b3c8ea","line":110,"updated":"2014-06-23 21:02:29.000000000","message":"Keystone*","commit_id":"611c844578e279455ba538cbe3220560cf41ca58"},{"author":{"_account_id":6482,"name":"Steve Martinelli","email":"s.martinelli@gmail.com","username":"stevemar"},"change_message_id":"e5cf88d1095b3554146d55f20a723d4c6c9a2035","unresolved":false,"context_lines":[{"line_number":107,"context_line":"should be considered to be a repeat of the above, only in the opposite"},{"line_number":108,"context_line":"direction."},{"line_number":109,"context_line":""},{"line_number":110,"context_line":"2. ACME\u0027s keystone mentioned in the above use cases above should"},{"line_number":111,"context_line":"have knowledge of what services and endpoints BETA offers so that"},{"line_number":112,"context_line":"it could build adequate token scope across both OpenStack clouds."},{"line_number":113,"context_line":"This can be done in a variety of ways. One idea is to allow ACME to"}],"source_content_type":"text/x-rst","patch_set":5,"id":"1ae5cdf2_3efc7c3f","line":110,"in_reply_to":"1ae5cdf2_c2b3c8ea","updated":"2014-06-24 02:59:59.000000000","message":"Done","commit_id":"611c844578e279455ba538cbe3220560cf41ca58"},{"author":{"_account_id":5046,"name":"Lance Bragstad","email":"lbragstad@redhat.com","username":"ldbragst"},"change_message_id":"9e5a4b180151058b149481e0a71df7abe1095824","unresolved":false,"context_lines":[{"line_number":114,"context_line":"poll BETA for a list of provided services and endpoints."},{"line_number":115,"context_line":""},{"line_number":116,"context_line":"3. The Keystone acting as a trusted service provider will get many tokens"},{"line_number":117,"context_line":"that are not within it\u0027s local store. It will need to be able to decipher"},{"line_number":118,"context_line":"what the originating Keystone is from the token in order to:"},{"line_number":119,"context_line":""},{"line_number":120,"context_line":"  1. Validate that the originating Keystone is listed as a trusted identity"}],"source_content_type":"text/x-rst","patch_set":5,"id":"1ae5cdf2_42f5f882","line":117,"updated":"2014-06-23 21:02:29.000000000","message":"its*","commit_id":"611c844578e279455ba538cbe3220560cf41ca58"},{"author":{"_account_id":6482,"name":"Steve Martinelli","email":"s.martinelli@gmail.com","username":"stevemar"},"change_message_id":"e5cf88d1095b3554146d55f20a723d4c6c9a2035","unresolved":false,"context_lines":[{"line_number":114,"context_line":"poll BETA for a list of provided services and endpoints."},{"line_number":115,"context_line":""},{"line_number":116,"context_line":"3. The Keystone acting as a trusted service provider will get many tokens"},{"line_number":117,"context_line":"that are not within it\u0027s local store. It will need to be able to decipher"},{"line_number":118,"context_line":"what the originating Keystone is from the token in order to:"},{"line_number":119,"context_line":""},{"line_number":120,"context_line":"  1. Validate that the originating Keystone is listed as a trusted identity"}],"source_content_type":"text/x-rst","patch_set":5,"id":"1ae5cdf2_5ef9484d","line":117,"in_reply_to":"1ae5cdf2_42f5f882","updated":"2014-06-24 02:59:59.000000000","message":"Done","commit_id":"611c844578e279455ba538cbe3220560cf41ca58"},{"author":{"_account_id":5046,"name":"Lance Bragstad","email":"lbragstad@redhat.com","username":"ldbragst"},"change_message_id":"9e5a4b180151058b149481e0a71df7abe1095824","unresolved":false,"context_lines":[{"line_number":232,"context_line":""},{"line_number":233,"context_line":"* stevemar"},{"line_number":234,"context_line":""},{"line_number":235,"context_line":"* marekd"},{"line_number":236,"context_line":""},{"line_number":237,"context_line":"Other contributors:"},{"line_number":238,"context_line":""}],"source_content_type":"text/x-rst","patch_set":5,"id":"1ae5cdf2_028130c3","line":235,"updated":"2014-06-23 21:02:29.000000000","message":"Full names and emails?","commit_id":"611c844578e279455ba538cbe3220560cf41ca58"},{"author":{"_account_id":6482,"name":"Steve Martinelli","email":"s.martinelli@gmail.com","username":"stevemar"},"change_message_id":"e5cf88d1095b3554146d55f20a723d4c6c9a2035","unresolved":false,"context_lines":[{"line_number":232,"context_line":""},{"line_number":233,"context_line":"* stevemar"},{"line_number":234,"context_line":""},{"line_number":235,"context_line":"* marekd"},{"line_number":236,"context_line":""},{"line_number":237,"context_line":"Other contributors:"},{"line_number":238,"context_line":""}],"source_content_type":"text/x-rst","patch_set":5,"id":"1ae5cdf2_9eb9107f","line":235,"in_reply_to":"1ae5cdf2_028130c3","updated":"2014-06-24 02:59:59.000000000","message":"Done","commit_id":"611c844578e279455ba538cbe3220560cf41ca58"},{"author":{"_account_id":5046,"name":"Lance Bragstad","email":"lbragstad@redhat.com","username":"ldbragst"},"change_message_id":"9e5a4b180151058b149481e0a71df7abe1095824","unresolved":false,"context_lines":[{"line_number":266,"context_line":""},{"line_number":267,"context_line":"* Add unit tests for the new REST APIs."},{"line_number":268,"context_line":""},{"line_number":269,"context_line":"* If possible, create tempest tests where multiple Keystones exist."},{"line_number":270,"context_line":""},{"line_number":271,"context_line":""},{"line_number":272,"context_line":"Documentation Impact"}],"source_content_type":"text/x-rst","patch_set":5,"id":"1ae5cdf2_a2715c0e","line":269,"updated":"2014-06-23 21:02:29.000000000","message":"s/Keystones/Keystone implementations/g","commit_id":"611c844578e279455ba538cbe3220560cf41ca58"},{"author":{"_account_id":6482,"name":"Steve Martinelli","email":"s.martinelli@gmail.com","username":"stevemar"},"change_message_id":"e5cf88d1095b3554146d55f20a723d4c6c9a2035","unresolved":false,"context_lines":[{"line_number":266,"context_line":""},{"line_number":267,"context_line":"* Add unit tests for the new REST APIs."},{"line_number":268,"context_line":""},{"line_number":269,"context_line":"* If possible, create tempest tests where multiple Keystones exist."},{"line_number":270,"context_line":""},{"line_number":271,"context_line":""},{"line_number":272,"context_line":"Documentation Impact"}],"source_content_type":"text/x-rst","patch_set":5,"id":"1ae5cdf2_bebecc62","line":269,"in_reply_to":"1ae5cdf2_a2715c0e","updated":"2014-06-24 02:59:59.000000000","message":"Done","commit_id":"611c844578e279455ba538cbe3220560cf41ca58"},{"author":{"_account_id":6482,"name":"Steve Martinelli","email":"s.martinelli@gmail.com","username":"stevemar"},"change_message_id":"ce885675fa1cb13dd3b50895d3c0233cd76b4f2c","unresolved":false,"context_lines":[{"line_number":23,"context_line":"* Cloud Implementer - The person or group of people deploying and configuring"},{"line_number":24,"context_line":"  an OpenStack cloud."},{"line_number":25,"context_line":""},{"line_number":26,"context_line":"* Cloud Service Provider (CSP) - A company that offers an OpenStack compatible"},{"line_number":27,"context_line":"  public cloud."},{"line_number":28,"context_line":""},{"line_number":29,"context_line":"* Identity provider (IdP) - The federated identity provider of the end user."}],"source_content_type":"text/x-rst","patch_set":6,"id":"1ae5cdf2_8956f728","line":26,"updated":"2014-06-25 15:42:24.000000000","message":"shortening this to just  Service Provider since we\u0027re using the two interchangeably anyway","commit_id":"8a811b5c8afe081080bea7e22e3a7d80bd359250"},{"author":{"_account_id":6460,"name":"Brad Topol","email":"btopol@us.ibm.com","username":"btopol"},"change_message_id":"daf69b485c2c851427d3c11d23bc3778ec0f67dd","unresolved":false,"context_lines":[{"line_number":37,"context_line":"that comes with provisioning identities in Keystone. Keystone trusts the"},{"line_number":38,"context_line":"IdP enough to **accept federated identities from** them."},{"line_number":39,"context_line":"However, there is no way right now for one Keystone to trust another Keystone."},{"line_number":40,"context_line":"This is where one Keystone trusts another to **assert federation identities"},{"line_number":41,"context_line":"to** it."},{"line_number":42,"context_line":""},{"line_number":43,"context_line":"This possibility has a couple cases, outlined below."}],"source_content_type":"text/x-rst","patch_set":6,"id":"1ae5cdf2_5102ed72","line":40,"updated":"2014-06-25 03:41:17.000000000","message":"Great description!","commit_id":"8a811b5c8afe081080bea7e22e3a7d80bd359250"},{"author":{"_account_id":6460,"name":"Brad Topol","email":"btopol@us.ibm.com","username":"btopol"},"change_message_id":"daf69b485c2c851427d3c11d23bc3778ec0f67dd","unresolved":false,"context_lines":[{"line_number":68,"context_line":""},{"line_number":69,"context_line":"**Use case 3: Multiple in-house OpenStack implementations:**"},{"line_number":70,"context_line":""},{"line_number":71,"context_line":"ACME has several OpenStack clouds setup, and each one maintains its"},{"line_number":72,"context_line":"own set of assignments. They would like to enable identity federation"},{"line_number":73,"context_line":"across their multiple clouds so that an identity accessing each cloud"},{"line_number":74,"context_line":"doesn\u0027t need to maintain several tokens and credentials."}],"source_content_type":"text/x-rst","patch_set":6,"id":"1ae5cdf2_f1f05994","line":71,"updated":"2014-06-25 03:41:17.000000000","message":"How is use case 3 different from use case 1?  They seem very similar.  Can you add a sentence on how 3 differs from 1?","commit_id":"8a811b5c8afe081080bea7e22e3a7d80bd359250"},{"author":{"_account_id":7725,"name":"David Stanek","email":"dstanek@dstanek.com","username":"dstanek"},"change_message_id":"2ecf9df7c24a8a9275548b1878add69cb191b08b","unresolved":false,"context_lines":[{"line_number":68,"context_line":""},{"line_number":69,"context_line":"**Use case 3: Multiple in-house OpenStack implementations:**"},{"line_number":70,"context_line":""},{"line_number":71,"context_line":"ACME has several OpenStack clouds setup, and each one maintains its"},{"line_number":72,"context_line":"own set of assignments. They would like to enable identity federation"},{"line_number":73,"context_line":"across their multiple clouds so that an identity accessing each cloud"},{"line_number":74,"context_line":"doesn\u0027t need to maintain several tokens and credentials."}],"source_content_type":"text/x-rst","patch_set":6,"id":"1ae5cdf2_5dc3c538","line":71,"in_reply_to":"1ae5cdf2_6cd61955","updated":"2014-06-25 16:58:36.000000000","message":"I don\u0027t mind having them both here. Maybe just adding re-seller to the one description would have it clearer.","commit_id":"8a811b5c8afe081080bea7e22e3a7d80bd359250"},{"author":{"_account_id":6482,"name":"Steve Martinelli","email":"s.martinelli@gmail.com","username":"stevemar"},"change_message_id":"ce885675fa1cb13dd3b50895d3c0233cd76b4f2c","unresolved":false,"context_lines":[{"line_number":68,"context_line":""},{"line_number":69,"context_line":"**Use case 3: Multiple in-house OpenStack implementations:**"},{"line_number":70,"context_line":""},{"line_number":71,"context_line":"ACME has several OpenStack clouds setup, and each one maintains its"},{"line_number":72,"context_line":"own set of assignments. They would like to enable identity federation"},{"line_number":73,"context_line":"across their multiple clouds so that an identity accessing each cloud"},{"line_number":74,"context_line":"doesn\u0027t need to maintain several tokens and credentials."}],"source_content_type":"text/x-rst","patch_set":6,"id":"1ae5cdf2_6cd61955","line":71,"in_reply_to":"1ae5cdf2_f1f05994","updated":"2014-06-25 15:42:24.000000000","message":"I think it\u0027s just in-house vs re-seller? \nNot sure this warrants it\u0027s own use case","commit_id":"8a811b5c8afe081080bea7e22e3a7d80bd359250"},{"author":{"_account_id":7725,"name":"David Stanek","email":"dstanek@dstanek.com","username":"dstanek"},"change_message_id":"7708e884b4b42bc18962ba10cf9d17b5748f31f2","unresolved":false,"context_lines":[{"line_number":78,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":79,"context_line":"**This proposal is 4 fold:**"},{"line_number":80,"context_line":""},{"line_number":81,"context_line":"1. Build the concept of a trusted service provider into Keystone."},{"line_number":82,"context_line":"Note that Keystone already has the concept of trusted service providers."},{"line_number":83,"context_line":"This is what the local Swift, Nova, and other OpenStack services are."},{"line_number":84,"context_line":"However, in this new context the service provider is an external service"}],"source_content_type":"text/x-rst","patch_set":6,"id":"1ae5cdf2_603d472c","line":81,"updated":"2014-06-25 14:55:01.000000000","message":"These two sentences sound strange together. \"Build this thing. This thing already exists.\"","commit_id":"8a811b5c8afe081080bea7e22e3a7d80bd359250"},{"author":{"_account_id":6482,"name":"Steve Martinelli","email":"s.martinelli@gmail.com","username":"stevemar"},"change_message_id":"ce885675fa1cb13dd3b50895d3c0233cd76b4f2c","unresolved":false,"context_lines":[{"line_number":78,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":79,"context_line":"**This proposal is 4 fold:**"},{"line_number":80,"context_line":""},{"line_number":81,"context_line":"1. Build the concept of a trusted service provider into Keystone."},{"line_number":82,"context_line":"Note that Keystone already has the concept of trusted service providers."},{"line_number":83,"context_line":"This is what the local Swift, Nova, and other OpenStack services are."},{"line_number":84,"context_line":"However, in this new context the service provider is an external service"}],"source_content_type":"text/x-rst","patch_set":6,"id":"1ae5cdf2_cc03adbc","line":81,"in_reply_to":"1ae5cdf2_603d472c","updated":"2014-06-25 15:42:24.000000000","message":"I see what you mean, it should be *locally trusted SPs\" or something like that. \nWe probably don\u0027t need to mention them as they don\u0027t help the greater scheme of external trusted SPs","commit_id":"8a811b5c8afe081080bea7e22e3a7d80bd359250"},{"author":{"_account_id":5956,"name":"Kristy Siu","email":"kwss@kent.ac.uk","username":"kwss"},"change_message_id":"870e5ed2c35aedcdc5c65ae2bb15f9f416c68662","unresolved":false,"context_lines":[{"line_number":82,"context_line":"Note that Keystone already has the concept of trusted service providers."},{"line_number":83,"context_line":"This is what the local Swift, Nova, and other OpenStack services are."},{"line_number":84,"context_line":"However, in this new context the service provider is an external service"},{"line_number":85,"context_line":"that the local Keystone trusts to **assert federated identities to** it."},{"line_number":86,"context_line":""},{"line_number":87,"context_line":"These are separate from the identity provider trust relationships we built"},{"line_number":88,"context_line":"in Icehouse. This will allow the cloud implementer to explicitly manage trust"}],"source_content_type":"text/x-rst","patch_set":6,"id":"1ae5cdf2_ecc1534f","line":85,"updated":"2014-06-25 11:48:21.000000000","message":"This is the wrong way round, the service provider Keystone should trust the local Keystone to assert identities to it.\n\n\"the service provider is an external service which trusts the local Keystone to **assert federated identities to** it.\"","commit_id":"8a811b5c8afe081080bea7e22e3a7d80bd359250"},{"author":{"_account_id":6482,"name":"Steve Martinelli","email":"s.martinelli@gmail.com","username":"stevemar"},"change_message_id":"ce885675fa1cb13dd3b50895d3c0233cd76b4f2c","unresolved":false,"context_lines":[{"line_number":82,"context_line":"Note that Keystone already has the concept of trusted service providers."},{"line_number":83,"context_line":"This is what the local Swift, Nova, and other OpenStack services are."},{"line_number":84,"context_line":"However, in this new context the service provider is an external service"},{"line_number":85,"context_line":"that the local Keystone trusts to **assert federated identities to** it."},{"line_number":86,"context_line":""},{"line_number":87,"context_line":"These are separate from the identity provider trust relationships we built"},{"line_number":88,"context_line":"in Icehouse. This will allow the cloud implementer to explicitly manage trust"}],"source_content_type":"text/x-rst","patch_set":6,"id":"1ae5cdf2_6cf299e4","line":85,"in_reply_to":"1ae5cdf2_ecc1534f","updated":"2014-06-25 15:42:24.000000000","message":"Right ++","commit_id":"8a811b5c8afe081080bea7e22e3a7d80bd359250"},{"author":{"_account_id":6460,"name":"Brad Topol","email":"btopol@us.ibm.com","username":"btopol"},"change_message_id":"daf69b485c2c851427d3c11d23bc3778ec0f67dd","unresolved":false,"context_lines":[{"line_number":91,"context_line":"a service provider, and \"BETA\" would trust \"ACME\" as an identity provider."},{"line_number":92,"context_line":"That will allow \"ACME\" to burst into \"BETA\" cloud but not the other way around."},{"line_number":93,"context_line":""},{"line_number":94,"context_line":"To keep things simple, we should only consider one trust relationship at a"},{"line_number":95,"context_line":"time (since trust is not commutative, nor bi-directional). So to establish"},{"line_number":96,"context_line":"one way trust between ACME and BETA, ACME would need to set up BETA as a"},{"line_number":97,"context_line":"trusted IdP. (BETA can do likewise if it wants to, but this is"}],"source_content_type":"text/x-rst","patch_set":6,"id":"1ae5cdf2_d13c3d33","line":94,"updated":"2014-06-25 03:41:17.000000000","message":"I like the one trust approach","commit_id":"8a811b5c8afe081080bea7e22e3a7d80bd359250"},{"author":{"_account_id":7725,"name":"David Stanek","email":"dstanek@dstanek.com","username":"dstanek"},"change_message_id":"7708e884b4b42bc18962ba10cf9d17b5748f31f2","unresolved":false,"context_lines":[{"line_number":109,"context_line":""},{"line_number":110,"context_line":"2. ACME\u0027s Keystone mentioned in the above use cases above should"},{"line_number":111,"context_line":"have knowledge of what services and endpoints BETA offers so that"},{"line_number":112,"context_line":"it could build adequate token scope across both OpenStack clouds."},{"line_number":113,"context_line":"This can be done in a variety of ways. One idea is to allow ACME to"},{"line_number":114,"context_line":"poll BETA for a list of provided services and endpoints."},{"line_number":115,"context_line":""}],"source_content_type":"text/x-rst","patch_set":6,"id":"1ae5cdf2_4014cb4c","line":112,"updated":"2014-06-25 14:55:01.000000000","message":"What are you going to be scoping the token to?","commit_id":"8a811b5c8afe081080bea7e22e3a7d80bd359250"},{"author":{"_account_id":6482,"name":"Steve Martinelli","email":"s.martinelli@gmail.com","username":"stevemar"},"change_message_id":"ce885675fa1cb13dd3b50895d3c0233cd76b4f2c","unresolved":false,"context_lines":[{"line_number":109,"context_line":""},{"line_number":110,"context_line":"2. ACME\u0027s Keystone mentioned in the above use cases above should"},{"line_number":111,"context_line":"have knowledge of what services and endpoints BETA offers so that"},{"line_number":112,"context_line":"it could build adequate token scope across both OpenStack clouds."},{"line_number":113,"context_line":"This can be done in a variety of ways. One idea is to allow ACME to"},{"line_number":114,"context_line":"poll BETA for a list of provided services and endpoints."},{"line_number":115,"context_line":""}],"source_content_type":"text/x-rst","patch_set":6,"id":"1ae5cdf2_ccb48dd6","line":112,"in_reply_to":"1ae5cdf2_4014cb4c","updated":"2014-06-25 15:42:24.000000000","message":"This is a bigger issue, lets say RAX sets up CERN as an idp and gives it a mapping. Then when a RAX user hits the federation auth URL, he should be given an unscoped token, like in the federtaion flow today. \n\nThen find the projects and domain he can get from there?","commit_id":"8a811b5c8afe081080bea7e22e3a7d80bd359250"},{"author":{"_account_id":7725,"name":"David Stanek","email":"dstanek@dstanek.com","username":"dstanek"},"change_message_id":"2ecf9df7c24a8a9275548b1878add69cb191b08b","unresolved":false,"context_lines":[{"line_number":109,"context_line":""},{"line_number":110,"context_line":"2. ACME\u0027s Keystone mentioned in the above use cases above should"},{"line_number":111,"context_line":"have knowledge of what services and endpoints BETA offers so that"},{"line_number":112,"context_line":"it could build adequate token scope across both OpenStack clouds."},{"line_number":113,"context_line":"This can be done in a variety of ways. One idea is to allow ACME to"},{"line_number":114,"context_line":"poll BETA for a list of provided services and endpoints."},{"line_number":115,"context_line":""}],"source_content_type":"text/x-rst","patch_set":6,"id":"1ae5cdf2_fd81f1c3","line":112,"in_reply_to":"1ae5cdf2_ccb48dd6","updated":"2014-06-25 16:58:36.000000000","message":"Maybe this just needs more detail around the federation flow. The way I read this is that the user will not do anything different. All of the federation stuff is handled keystone-\u003ekeystone in the background.","commit_id":"8a811b5c8afe081080bea7e22e3a7d80bd359250"},{"author":{"_account_id":6482,"name":"Steve Martinelli","email":"s.martinelli@gmail.com","username":"stevemar"},"change_message_id":"ce885675fa1cb13dd3b50895d3c0233cd76b4f2c","unresolved":false,"context_lines":[{"line_number":111,"context_line":"have knowledge of what services and endpoints BETA offers so that"},{"line_number":112,"context_line":"it could build adequate token scope across both OpenStack clouds."},{"line_number":113,"context_line":"This can be done in a variety of ways. One idea is to allow ACME to"},{"line_number":114,"context_line":"poll BETA for a list of provided services and endpoints."},{"line_number":115,"context_line":""},{"line_number":116,"context_line":"3. The Keystone acting as a trusted service provider will get many tokens"},{"line_number":117,"context_line":"that are not within its local store. It will need to be able to decipher"}],"source_content_type":"text/x-rst","patch_set":6,"id":"1ae5cdf2_ec05c979","line":114,"updated":"2014-06-25 15:42:24.000000000","message":"Polling seems like a lot of work, and it\u0027s frequency will cause debate. \n\nI kind of like the idea of adding endpoints when registering a SP. There will be some out of band communication anyway, may as well say that endpoints are conveyed out of band too.","commit_id":"8a811b5c8afe081080bea7e22e3a7d80bd359250"},{"author":{"_account_id":7725,"name":"David Stanek","email":"dstanek@dstanek.com","username":"dstanek"},"change_message_id":"2ecf9df7c24a8a9275548b1878add69cb191b08b","unresolved":false,"context_lines":[{"line_number":111,"context_line":"have knowledge of what services and endpoints BETA offers so that"},{"line_number":112,"context_line":"it could build adequate token scope across both OpenStack clouds."},{"line_number":113,"context_line":"This can be done in a variety of ways. One idea is to allow ACME to"},{"line_number":114,"context_line":"poll BETA for a list of provided services and endpoints."},{"line_number":115,"context_line":""},{"line_number":116,"context_line":"3. The Keystone acting as a trusted service provider will get many tokens"},{"line_number":117,"context_line":"that are not within its local store. It will need to be able to decipher"}],"source_content_type":"text/x-rst","patch_set":6,"id":"1ae5cdf2_3d527968","line":114,"in_reply_to":"1ae5cdf2_ec05c979","updated":"2014-06-25 16:58:36.000000000","message":"I don\u0027t mind polling if the frequency is controlled by the remote service provider. This can easily be done by specifying the correct HTTP cache headers.","commit_id":"8a811b5c8afe081080bea7e22e3a7d80bd359250"},{"author":{"_account_id":7725,"name":"David Stanek","email":"dstanek@dstanek.com","username":"dstanek"},"change_message_id":"7708e884b4b42bc18962ba10cf9d17b5748f31f2","unresolved":false,"context_lines":[{"line_number":148,"context_line":"about where the tokens work, and must be able to handle multiple tokens."},{"line_number":149,"context_line":""},{"line_number":150,"context_line":"Data Model Impact"},{"line_number":151,"context_line":"-----------------"},{"line_number":152,"context_line":""},{"line_number":153,"context_line":"The concept of service providers would likely include new data objects and"},{"line_number":154,"context_line":"schema changes. The data objects and schema changes should be additive in"}],"source_content_type":"text/x-rst","patch_set":6,"id":"1ae5cdf2_39ad369c","line":151,"updated":"2014-06-25 14:55:01.000000000","message":"Do you have an idea of what the data model will look like? Key fields, etc.","commit_id":"8a811b5c8afe081080bea7e22e3a7d80bd359250"},{"author":{"_account_id":6482,"name":"Steve Martinelli","email":"s.martinelli@gmail.com","username":"stevemar"},"change_message_id":"ce885675fa1cb13dd3b50895d3c0233cd76b4f2c","unresolved":false,"context_lines":[{"line_number":148,"context_line":"about where the tokens work, and must be able to handle multiple tokens."},{"line_number":149,"context_line":""},{"line_number":150,"context_line":"Data Model Impact"},{"line_number":151,"context_line":"-----------------"},{"line_number":152,"context_line":""},{"line_number":153,"context_line":"The concept of service providers would likely include new data objects and"},{"line_number":154,"context_line":"schema changes. The data objects and schema changes should be additive in"}],"source_content_type":"text/x-rst","patch_set":6,"id":"1ae5cdf2_296fa3fd","line":151,"in_reply_to":"1ae5cdf2_39ad369c","updated":"2014-06-25 15:42:24.000000000","message":"SP:\n  id will be a name, like we have for IdP\n  description: like it says\n  additional_service_catalog_entries: [ list of things you want to share to the service catalog]\n\nIdP:\n  might have to create a new field to store the SP keys?","commit_id":"8a811b5c8afe081080bea7e22e3a7d80bd359250"},{"author":{"_account_id":5956,"name":"Kristy Siu","email":"kwss@kent.ac.uk","username":"kwss"},"change_message_id":"870e5ed2c35aedcdc5c65ae2bb15f9f416c68662","unresolved":false,"context_lines":[{"line_number":152,"context_line":""},{"line_number":153,"context_line":"The concept of service providers would likely include new data objects and"},{"line_number":154,"context_line":"schema changes. The data objects and schema changes should be additive in"},{"line_number":155,"context_line":"nature so as to not cause database migration complexity."},{"line_number":156,"context_line":""},{"line_number":157,"context_line":"REST API Impact"},{"line_number":158,"context_line":"---------------"}],"source_content_type":"text/x-rst","patch_set":6,"id":"1ae5cdf2_2c06db85","line":155,"updated":"2014-06-25 11:48:21.000000000","message":"Will the existing identity provider data model need to be changed or a new model added to allow for storing the signing keys of an external Keystone IdP?","commit_id":"8a811b5c8afe081080bea7e22e3a7d80bd359250"},{"author":{"_account_id":7725,"name":"David Stanek","email":"dstanek@dstanek.com","username":"dstanek"},"change_message_id":"7708e884b4b42bc18962ba10cf9d17b5748f31f2","unresolved":false,"context_lines":[{"line_number":157,"context_line":"REST API Impact"},{"line_number":158,"context_line":"---------------"},{"line_number":159,"context_line":""},{"line_number":160,"context_line":"* Register an service provider: ``PUT /OS-FEDERATION/service_providers/{sp_id}``"},{"line_number":161,"context_line":""},{"line_number":162,"context_line":"* List service providers: ``GET /OS-FEDERATION/service_providers``"},{"line_number":163,"context_line":""}],"source_content_type":"text/x-rst","patch_set":6,"id":"1ae5cdf2_99ef2ae9","line":160,"updated":"2014-06-25 14:55:01.000000000","message":"s/an/a/","commit_id":"8a811b5c8afe081080bea7e22e3a7d80bd359250"},{"author":{"_account_id":5956,"name":"Kristy Siu","email":"kwss@kent.ac.uk","username":"kwss"},"change_message_id":"870e5ed2c35aedcdc5c65ae2bb15f9f416c68662","unresolved":false,"context_lines":[{"line_number":175,"context_line":""},{"line_number":176,"context_line":"* Update the attribute mapping for an service provider and protocol combination: ``PATCH /OS-FEDERATION/service_providers/{sp_id}/protocols/{protocol_id}``"},{"line_number":177,"context_line":""},{"line_number":178,"context_line":"* Delete a supported protocol and attribute mapping combination from an identity provider: ``DELETE /OS-FEDERATION/service_providers/{idp_id}/protocols/{protocol_id}``"},{"line_number":179,"context_line":""},{"line_number":180,"context_line":""},{"line_number":181,"context_line":"Security Impact"}],"source_content_type":"text/x-rst","patch_set":6,"id":"1ae5cdf2_cc4c97cb","line":178,"updated":"2014-06-25 11:48:21.000000000","message":"These are unnecessary as the SP should not need to map attributes. The existing mapping interface can be used to manage mappings for external keystone tokens - /OS-FEDERATION/identity_providers/{idp_id}/protocols/{protocol_id}","commit_id":"8a811b5c8afe081080bea7e22e3a7d80bd359250"},{"author":{"_account_id":6482,"name":"Steve Martinelli","email":"s.martinelli@gmail.com","username":"stevemar"},"change_message_id":"ce885675fa1cb13dd3b50895d3c0233cd76b4f2c","unresolved":false,"context_lines":[{"line_number":175,"context_line":""},{"line_number":176,"context_line":"* Update the attribute mapping for an service provider and protocol combination: ``PATCH /OS-FEDERATION/service_providers/{sp_id}/protocols/{protocol_id}``"},{"line_number":177,"context_line":""},{"line_number":178,"context_line":"* Delete a supported protocol and attribute mapping combination from an identity provider: ``DELETE /OS-FEDERATION/service_providers/{idp_id}/protocols/{protocol_id}``"},{"line_number":179,"context_line":""},{"line_number":180,"context_line":""},{"line_number":181,"context_line":"Security Impact"}],"source_content_type":"text/x-rst","patch_set":6,"id":"1ae5cdf2_8566dd53","line":178,"in_reply_to":"1ae5cdf2_cc4c97cb","updated":"2014-06-25 15:42:24.000000000","message":"++ agree, we just need CRUD for service providers (for now)","commit_id":"8a811b5c8afe081080bea7e22e3a7d80bd359250"},{"author":{"_account_id":7725,"name":"David Stanek","email":"dstanek@dstanek.com","username":"dstanek"},"change_message_id":"7708e884b4b42bc18962ba10cf9d17b5748f31f2","unresolved":false,"context_lines":[{"line_number":243,"context_line":""},{"line_number":244,"context_line":"* Define a specification for adding and maintaining service providers."},{"line_number":245,"context_line":""},{"line_number":246,"context_line":"* Define and implement a publishing services the local Keystone has setup."},{"line_number":247,"context_line":"  (ex: \"nova\" at \"https://nova.acme.com\": TODO)"},{"line_number":248,"context_line":""},{"line_number":249,"context_line":"* Define and implement a method for listening to foreign Keystones"}],"source_content_type":"text/x-rst","patch_set":6,"id":"1ae5cdf2_398536cf","line":246,"updated":"2014-06-25 14:55:01.000000000","message":"What is being published?","commit_id":"8a811b5c8afe081080bea7e22e3a7d80bd359250"},{"author":{"_account_id":6482,"name":"Steve Martinelli","email":"s.martinelli@gmail.com","username":"stevemar"},"change_message_id":"ce885675fa1cb13dd3b50895d3c0233cd76b4f2c","unresolved":false,"context_lines":[{"line_number":243,"context_line":""},{"line_number":244,"context_line":"* Define a specification for adding and maintaining service providers."},{"line_number":245,"context_line":""},{"line_number":246,"context_line":"* Define and implement a publishing services the local Keystone has setup."},{"line_number":247,"context_line":"  (ex: \"nova\" at \"https://nova.acme.com\": TODO)"},{"line_number":248,"context_line":""},{"line_number":249,"context_line":"* Define and implement a method for listening to foreign Keystones"}],"source_content_type":"text/x-rst","patch_set":6,"id":"1ae5cdf2_295c037d","line":246,"in_reply_to":"1ae5cdf2_398536cf","updated":"2014-06-25 15:42:24.000000000","message":"I think this is an artifact of an initial proposal, removing","commit_id":"8a811b5c8afe081080bea7e22e3a7d80bd359250"},{"author":{"_account_id":7725,"name":"David Stanek","email":"dstanek@dstanek.com","username":"dstanek"},"change_message_id":"7708e884b4b42bc18962ba10cf9d17b5748f31f2","unresolved":false,"context_lines":[{"line_number":246,"context_line":"* Define and implement a publishing services the local Keystone has setup."},{"line_number":247,"context_line":"  (ex: \"nova\" at \"https://nova.acme.com\": TODO)"},{"line_number":248,"context_line":""},{"line_number":249,"context_line":"* Define and implement a method for listening to foreign Keystones"},{"line_number":250,"context_line":"  (ex: beta-keystone supports \"swift\" at \"https://swift.beta.com\": TODO)"},{"line_number":251,"context_line":""},{"line_number":252,"context_line":"* Define and implement a method of validating foreign tokens: TODO"}],"source_content_type":"text/x-rst","patch_set":6,"id":"1ae5cdf2_794dfec4","line":249,"updated":"2014-06-25 14:55:01.000000000","message":"What exactly is this? I don\u0027t see what this is from the \u0027Proposed Change\u0027 section.","commit_id":"8a811b5c8afe081080bea7e22e3a7d80bd359250"},{"author":{"_account_id":6482,"name":"Steve Martinelli","email":"s.martinelli@gmail.com","username":"stevemar"},"change_message_id":"ce885675fa1cb13dd3b50895d3c0233cd76b4f2c","unresolved":false,"context_lines":[{"line_number":246,"context_line":"* Define and implement a publishing services the local Keystone has setup."},{"line_number":247,"context_line":"  (ex: \"nova\" at \"https://nova.acme.com\": TODO)"},{"line_number":248,"context_line":""},{"line_number":249,"context_line":"* Define and implement a method for listening to foreign Keystones"},{"line_number":250,"context_line":"  (ex: beta-keystone supports \"swift\" at \"https://swift.beta.com\": TODO)"},{"line_number":251,"context_line":""},{"line_number":252,"context_line":"* Define and implement a method of validating foreign tokens: TODO"}],"source_content_type":"text/x-rst","patch_set":6,"id":"1ae5cdf2_0959078e","line":249,"in_reply_to":"1ae5cdf2_794dfec4","updated":"2014-06-25 15:42:24.000000000","message":"I think this is an artifact of an initial proposal, removing","commit_id":"8a811b5c8afe081080bea7e22e3a7d80bd359250"},{"author":{"_account_id":6482,"name":"Steve Martinelli","email":"s.martinelli@gmail.com","username":"stevemar"},"change_message_id":"ce885675fa1cb13dd3b50895d3c0233cd76b4f2c","unresolved":false,"context_lines":[{"line_number":254,"context_line":"* Define and implement a method of invalidating tokens across service"},{"line_number":255,"context_line":"  providers: TODO"},{"line_number":256,"context_line":""},{"line_number":257,"context_line":""},{"line_number":258,"context_line":"Dependencies"},{"line_number":259,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":260,"context_line":""}],"source_content_type":"text/x-rst","patch_set":6,"id":"1ae5cdf2_89fa7741","line":257,"updated":"2014-06-25 15:42:24.000000000","message":"* Define an implement a method for a service provide to store keys","commit_id":"8a811b5c8afe081080bea7e22e3a7d80bd359250"},{"author":{"_account_id":6534,"name":"David Chadwick","email":"d.w.chadwick@truetrust.co.uk","username":"d-w-chadwick"},"change_message_id":"79fc82a12af6e9598122ca68f9aeee585de3ca0f","unresolved":false,"context_lines":[{"line_number":24,"context_line":"  an OpenStack cloud."},{"line_number":25,"context_line":""},{"line_number":26,"context_line":"* Service Provider (SP) - An entity that offers an OpenStack compatible"},{"line_number":27,"context_line":"  public cloud."},{"line_number":28,"context_line":""},{"line_number":29,"context_line":"* Identity provider (IdP) - The federated identity provider of the end user."},{"line_number":30,"context_line":"  The service responsible for managing the authentication of the end user."}],"source_content_type":"text/x-rst","patch_set":9,"id":"1ae5cdf2_adcf24b2","line":27,"updated":"2014-06-26 05:35:31.000000000","message":"cloud service (public or private)","commit_id":"d67a84860835944fb4b733379b62fbf396800d28"},{"author":{"_account_id":6482,"name":"Steve Martinelli","email":"s.martinelli@gmail.com","username":"stevemar"},"change_message_id":"5cd319d5318a57a16466724ae24b11e0b5c792cc","unresolved":false,"context_lines":[{"line_number":24,"context_line":"  an OpenStack cloud."},{"line_number":25,"context_line":""},{"line_number":26,"context_line":"* Service Provider (SP) - An entity that offers an OpenStack compatible"},{"line_number":27,"context_line":"  public cloud."},{"line_number":28,"context_line":""},{"line_number":29,"context_line":"* Identity provider (IdP) - The federated identity provider of the end user."},{"line_number":30,"context_line":"  The service responsible for managing the authentication of the end user."}],"source_content_type":"text/x-rst","patch_set":9,"id":"1ae5cdf2_e84e7a95","line":27,"in_reply_to":"1ae5cdf2_adcf24b2","updated":"2014-06-26 06:30:28.000000000","message":"will update","commit_id":"d67a84860835944fb4b733379b62fbf396800d28"},{"author":{"_account_id":2903,"name":"Morgan Fainberg","email":"morgan.fainberg@gmail.com","username":"mdrnstm"},"change_message_id":"ebe6b6608e6dc9e7bde10cad15d3ab3e7bbfe152","unresolved":false,"context_lines":[{"line_number":73,"context_line":"service endpoints, and no others. Furthermore, the storage provider may wish"},{"line_number":74,"context_line":"to enforce access policies (who can access which containers) based on the set"},{"line_number":75,"context_line":"of roles that it defines. Hence, the User\u0027s Keystone must be able to acquire"},{"line_number":76,"context_line":"this set of roles and assign them to users accordingly."},{"line_number":77,"context_line":""},{"line_number":78,"context_line":""},{"line_number":79,"context_line":"**Note**, in all cases the end users currently using OpenStack clients"}],"source_content_type":"text/x-rst","patch_set":9,"id":"1ae5cdf2_4dd94082","line":76,"updated":"2014-06-26 05:23:40.000000000","message":"The specifically called out use-cases is great!","commit_id":"d67a84860835944fb4b733379b62fbf396800d28"},{"author":{"_account_id":6534,"name":"David Chadwick","email":"d.w.chadwick@truetrust.co.uk","username":"d-w-chadwick"},"change_message_id":"79fc82a12af6e9598122ca68f9aeee585de3ca0f","unresolved":false,"context_lines":[{"line_number":81,"context_line":"continue to do so without any changes. The current user-experience,"},{"line_number":82,"context_line":"that is used with non-federation-aware clients, should not need to change."},{"line_number":83,"context_line":""},{"line_number":84,"context_line":""},{"line_number":85,"context_line":"Proposed Change"},{"line_number":86,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":87,"context_line":""}],"source_content_type":"text/x-rst","patch_set":9,"id":"1ae5cdf2_2d715477","line":84,"updated":"2014-06-26 05:35:31.000000000","message":"replace the above Note with the following set of Requirements. (unless we can all agree explicitly on the requirements, we will all have different assumptions about what they are or should be)\n\nRequirements  \n\n\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\n\n1. The solution needs to be recursive, so that if Cloud A burst to Cloud B when it is overloaded, and Cloud B burst to Cloud C when it is overloaded, then jobs from A can be burst to C via B.\n\n2. The solution needs to require minimum changes to existing non-Keystone components i.e. both clients and OpenStack services, or to put it another way, the majority of the changes should be applied to keystone\n\n3A. If changes have to be applied to either clients or OpenStack services, then changes to clients should take precedence over changes to OpenStack services. It would be optimum if only the Keystone client needs to change in this situation OR\n3B. The current user-experience, that is used by non-federation-aware clients, should not need to change. Thus changes to service should take precedence over changes to clients\n\n4. The solution must be as secure as the existing implementation of Keystone and Openstack i.e. we must not downgrade the overall security by the introduction of Keystone federation. On the other hand it does not need to be more secure since attackers will always go for the weakest link\n\n5. The solution must not reduce the functionality of existing clients and services\n\n6. The solution must work for federated users and non-federated users\n\n7. The solution should not unduly impact on the non-functional aspects of existing OpenStack services e.g. performance, scalability etc.\n\n8. The local Keystone administrator must be able to have full control over the external entities that he trusts. This is relatively easy to achieve for direct trust relationships. but is more complex for indirect trust relationships e.g. Keystone A trusts IdP 1 and external Keystone B, but not IdP2. Keystone B trusts IdP 1 and IdP 2. Keystone A must be able to stop users from IdP2 authenticating to Keystone B and then accessing its services via this indirect route.\n\n9. Should a token be revoked (either by its holder or issuer), there needs to be some way for all recipients (i.e. CSPs) to know about this. E.g. there is a revocation service that the recipient can contact, or the issuer  broadcasts out to its trusted CSPs, so that the revocation is all encompassing. The alternative is for the IdP to issue short lived tokens that will never be revoked e.g. as in SAML. Keystone should be able to handle both of these scenarios.","commit_id":"d67a84860835944fb4b733379b62fbf396800d28"},{"author":{"_account_id":6482,"name":"Steve Martinelli","email":"s.martinelli@gmail.com","username":"stevemar"},"change_message_id":"5cd319d5318a57a16466724ae24b11e0b5c792cc","unresolved":false,"context_lines":[{"line_number":81,"context_line":"continue to do so without any changes. The current user-experience,"},{"line_number":82,"context_line":"that is used with non-federation-aware clients, should not need to change."},{"line_number":83,"context_line":""},{"line_number":84,"context_line":""},{"line_number":85,"context_line":"Proposed Change"},{"line_number":86,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":87,"context_line":""}],"source_content_type":"text/x-rst","patch_set":9,"id":"1ae5cdf2_c37361b2","line":84,"in_reply_to":"1ae5cdf2_2d715477","updated":"2014-06-26 06:30:28.000000000","message":"So, I\u0027m cool with replacing the note with what you have written. \n\nSome remarks,\n\n- I\u0027m worried about the implementation of #1, since I hadn\u0027t thought of it, it seems daunting.\n\n- I think if I proposed anything that didn\u0027t meet 4/5/6/7 then dolphm would ban me from anything keystone related.","commit_id":"d67a84860835944fb4b733379b62fbf396800d28"},{"author":{"_account_id":8978,"name":"Marek Denis","email":"marek.denis+openstack@gmail.com","username":"marek-denis"},"change_message_id":"4d198b07fbcbe5c5fd8b5bb23c9cf395bad4e606","unresolved":false,"context_lines":[{"line_number":81,"context_line":"continue to do so without any changes. The current user-experience,"},{"line_number":82,"context_line":"that is used with non-federation-aware clients, should not need to change."},{"line_number":83,"context_line":""},{"line_number":84,"context_line":""},{"line_number":85,"context_line":"Proposed Change"},{"line_number":86,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":87,"context_line":""}],"source_content_type":"text/x-rst","patch_set":9,"id":"1ae5cdf2_5ed9e481","line":84,"in_reply_to":"1ae5cdf2_c37361b2","updated":"2014-06-26 09:38:54.000000000","message":"Steve++. I\u0027d wait with req #1 for another releases, when we have basic functionality implemented.","commit_id":"d67a84860835944fb4b733379b62fbf396800d28"},{"author":{"_account_id":6534,"name":"David Chadwick","email":"d.w.chadwick@truetrust.co.uk","username":"d-w-chadwick"},"change_message_id":"79fc82a12af6e9598122ca68f9aeee585de3ca0f","unresolved":false,"context_lines":[{"line_number":105,"context_line":"2. ACME\u0027s Keystone mentioned in the above use cases above should"},{"line_number":106,"context_line":"have knowledge of what services and endpoints BETA offers so that"},{"line_number":107,"context_line":"it could build adequate token scope across both OpenStack clouds."},{"line_number":108,"context_line":""},{"line_number":109,"context_line":"3. BETA\u0027s Keystone, acting as a trusted service provider, will get many tokens"},{"line_number":110,"context_line":"that are not within its local store. It will need to be able to decipher"},{"line_number":111,"context_line":"where the originating Keystone is from:"}],"source_content_type":"text/x-rst","patch_set":9,"id":"1ae5cdf2_4dc6a04a","line":108,"updated":"2014-06-26 05:35:31.000000000","message":"3. Improve the way that the concept of trusted Identity Providers is handled in Keystone, to cater for gateways and proxy IdPs.\n\nThe issue of trust gets more complex if a trusted intermediary, say GAMMA, validates the identity token issued by BETA. (GAMMA could be a remote Keystone, or an Apache front end of ACME). In this case ACME will never see the token issued by BETA, but will receive the token issued by GAMMA the trusted intermediary. This means that the trusted intermediary must say in its token who the original IdP was. In this way, ACME can look at its trust rules to determine if the token from the intermediary should be accepted or not. ACME must have trust rules to say that both GAMMA and BETA are trusted, but the rules will be different. BETA will be a trusted IdP and GAMMA will be a trusted gateway or proxy IdP. (Note that a remote Keystone could be configured twice, once as a trusted gateway when its users are authenticated by a remote IdP that it trusts, and once as an IdP when Keystone has a backend LDAP holding the un/pws of its users.)\n\nThe picture here \n\nhttp://www.slideshare.net/davidwchadwick/keystone-trust \n\nshows how the trust rules should operate","commit_id":"d67a84860835944fb4b733379b62fbf396800d28"},{"author":{"_account_id":6534,"name":"David Chadwick","email":"d.w.chadwick@truetrust.co.uk","username":"d-w-chadwick"},"change_message_id":"79fc82a12af6e9598122ca68f9aeee585de3ca0f","unresolved":false,"context_lines":[{"line_number":110,"context_line":"that are not within its local store. It will need to be able to decipher"},{"line_number":111,"context_line":"where the originating Keystone is from:"},{"line_number":112,"context_line":""},{"line_number":113,"context_line":"  1. Validate that the originating Keystone is listed as a trusted IdP."},{"line_number":114,"context_line":"  If using PKI tokens, the SignerInfo field in CMS should tell us where it is"},{"line_number":115,"context_line":"  coming from. http://tools.ietf.org/html/rfc5652#section-5.3"},{"line_number":116,"context_line":""}],"source_content_type":"text/x-rst","patch_set":9,"id":"1ae5cdf2_0dff3867","line":113,"updated":"2014-06-26 05:35:31.000000000","message":"trusted IdP or proxy IdP.","commit_id":"d67a84860835944fb4b733379b62fbf396800d28"},{"author":{"_account_id":6482,"name":"Steve Martinelli","email":"s.martinelli@gmail.com","username":"stevemar"},"change_message_id":"5cd319d5318a57a16466724ae24b11e0b5c792cc","unresolved":false,"context_lines":[{"line_number":110,"context_line":"that are not within its local store. It will need to be able to decipher"},{"line_number":111,"context_line":"where the originating Keystone is from:"},{"line_number":112,"context_line":""},{"line_number":113,"context_line":"  1. Validate that the originating Keystone is listed as a trusted IdP."},{"line_number":114,"context_line":"  If using PKI tokens, the SignerInfo field in CMS should tell us where it is"},{"line_number":115,"context_line":"  coming from. http://tools.ietf.org/html/rfc5652#section-5.3"},{"line_number":116,"context_line":""}],"source_content_type":"text/x-rst","patch_set":9,"id":"1ae5cdf2_88533639","line":113,"in_reply_to":"1ae5cdf2_0dff3867","updated":"2014-06-26 06:30:28.000000000","message":"Done","commit_id":"d67a84860835944fb4b733379b62fbf396800d28"},{"author":{"_account_id":6534,"name":"David Chadwick","email":"d.w.chadwick@truetrust.co.uk","username":"d-w-chadwick"},"change_message_id":"79fc82a12af6e9598122ca68f9aeee585de3ca0f","unresolved":false,"context_lines":[{"line_number":113,"context_line":"  1. Validate that the originating Keystone is listed as a trusted IdP."},{"line_number":114,"context_line":"  If using PKI tokens, the SignerInfo field in CMS should tell us where it is"},{"line_number":115,"context_line":"  coming from. http://tools.ietf.org/html/rfc5652#section-5.3"},{"line_number":116,"context_line":""},{"line_number":117,"context_line":"  2. Initiate the federation handshake with that originating Keystone to"},{"line_number":118,"context_line":"  validate the token and issue another token based on mapped properties."},{"line_number":119,"context_line":""}],"source_content_type":"text/x-rst","patch_set":9,"id":"1ae5cdf2_ed304c57","line":116,"updated":"2014-06-26 05:35:31.000000000","message":"There are two ways (at least) that tokens can be validated\n\n        1) the token is self contained e.g. PKI token, and the recipient can validate it given some pre-configured trust information (e.g. Root CA public key)\n\n        2) the token must be returned to the originator asking it if it is valid or not.\n\nWhich of the above do we plan to support? 1) 2) or both?","commit_id":"d67a84860835944fb4b733379b62fbf396800d28"},{"author":{"_account_id":6482,"name":"Steve Martinelli","email":"s.martinelli@gmail.com","username":"stevemar"},"change_message_id":"96d24c9667c36a4dc4b7b3e8af9f9707d8197c9b","unresolved":false,"context_lines":[{"line_number":113,"context_line":"  1. Validate that the originating Keystone is listed as a trusted IdP."},{"line_number":114,"context_line":"  If using PKI tokens, the SignerInfo field in CMS should tell us where it is"},{"line_number":115,"context_line":"  coming from. http://tools.ietf.org/html/rfc5652#section-5.3"},{"line_number":116,"context_line":""},{"line_number":117,"context_line":"  2. Initiate the federation handshake with that originating Keystone to"},{"line_number":118,"context_line":"  validate the token and issue another token based on mapped properties."},{"line_number":119,"context_line":""}],"source_content_type":"text/x-rst","patch_set":9,"id":"1ae5cdf2_5f5b9485","line":116,"in_reply_to":"1ae5cdf2_29177aa4","updated":"2014-06-26 14:39:57.000000000","message":"We\u0027ve been pushing PKI tokens for a few releases now, there are several benefits to using PKI tokens. I\u0027m fine with taking a stance on using PKI tokens is a requirements here. (I think dolphm would agree)","commit_id":"d67a84860835944fb4b733379b62fbf396800d28"},{"author":{"_account_id":5956,"name":"Kristy Siu","email":"kwss@kent.ac.uk","username":"kwss"},"change_message_id":"2b1a841b4e5b436be2ead6e5fec0234e5e5c69e8","unresolved":false,"context_lines":[{"line_number":113,"context_line":"  1. Validate that the originating Keystone is listed as a trusted IdP."},{"line_number":114,"context_line":"  If using PKI tokens, the SignerInfo field in CMS should tell us where it is"},{"line_number":115,"context_line":"  coming from. http://tools.ietf.org/html/rfc5652#section-5.3"},{"line_number":116,"context_line":""},{"line_number":117,"context_line":"  2. Initiate the federation handshake with that originating Keystone to"},{"line_number":118,"context_line":"  validate the token and issue another token based on mapped properties."},{"line_number":119,"context_line":""}],"source_content_type":"text/x-rst","patch_set":9,"id":"1ae5cdf2_29177aa4","line":116,"in_reply_to":"1ae5cdf2_de3b349a","updated":"2014-06-26 13:22:27.000000000","message":"#1 is good but only if the token is PKI? What about Keystone deployments not using PKI, will they also be supported? How do we determine issuer when this is the case?","commit_id":"d67a84860835944fb4b733379b62fbf396800d28"},{"author":{"_account_id":8978,"name":"Marek Denis","email":"marek.denis+openstack@gmail.com","username":"marek-denis"},"change_message_id":"4d198b07fbcbe5c5fd8b5bb23c9cf395bad4e606","unresolved":false,"context_lines":[{"line_number":113,"context_line":"  1. Validate that the originating Keystone is listed as a trusted IdP."},{"line_number":114,"context_line":"  If using PKI tokens, the SignerInfo field in CMS should tell us where it is"},{"line_number":115,"context_line":"  coming from. http://tools.ietf.org/html/rfc5652#section-5.3"},{"line_number":116,"context_line":""},{"line_number":117,"context_line":"  2. Initiate the federation handshake with that originating Keystone to"},{"line_number":118,"context_line":"  validate the token and issue another token based on mapped properties."},{"line_number":119,"context_line":""}],"source_content_type":"text/x-rst","patch_set":9,"id":"1ae5cdf2_de3b349a","line":116,"in_reply_to":"1ae5cdf2_e8359af7","updated":"2014-06-26 09:38:54.000000000","message":"+ for #1","commit_id":"d67a84860835944fb4b733379b62fbf396800d28"},{"author":{"_account_id":6482,"name":"Steve Martinelli","email":"s.martinelli@gmail.com","username":"stevemar"},"change_message_id":"5cd319d5318a57a16466724ae24b11e0b5c792cc","unresolved":false,"context_lines":[{"line_number":113,"context_line":"  1. Validate that the originating Keystone is listed as a trusted IdP."},{"line_number":114,"context_line":"  If using PKI tokens, the SignerInfo field in CMS should tell us where it is"},{"line_number":115,"context_line":"  coming from. http://tools.ietf.org/html/rfc5652#section-5.3"},{"line_number":116,"context_line":""},{"line_number":117,"context_line":"  2. Initiate the federation handshake with that originating Keystone to"},{"line_number":118,"context_line":"  validate the token and issue another token based on mapped properties."},{"line_number":119,"context_line":""}],"source_content_type":"text/x-rst","patch_set":9,"id":"1ae5cdf2_e8359af7","line":116,"in_reply_to":"1ae5cdf2_ed304c57","updated":"2014-06-26 06:30:28.000000000","message":"I think #1 is preferred, as it\u0027s 1 less trip back to Keystone.","commit_id":"d67a84860835944fb4b733379b62fbf396800d28"},{"author":{"_account_id":6482,"name":"Steve Martinelli","email":"s.martinelli@gmail.com","username":"stevemar"},"change_message_id":"5cd319d5318a57a16466724ae24b11e0b5c792cc","unresolved":false,"context_lines":[{"line_number":146,"context_line":"        Within the request it contains BETAs authentication URL,"},{"line_number":147,"context_line":"        which was obtained out of band."},{"line_number":148,"context_line":""},{"line_number":149,"context_line":"   (B)\tCloud Implementer at BETA adds ACME as a trusted IdP via:"},{"line_number":150,"context_line":"        PUT http://BETA.COM/v3/OS-FEDERATION/identity_provider/ACME"},{"line_number":151,"context_line":"        Within the request it contains a public key that can be used"},{"line_number":152,"context_line":"        to verify signatures from ACME issued tokens."}],"source_content_type":"text/x-rst","patch_set":9,"id":"1ae5cdf2_083726ff","line":149,"updated":"2014-06-26 06:30:28.000000000","message":"another hard tab","commit_id":"d67a84860835944fb4b733379b62fbf396800d28"},{"author":{"_account_id":6482,"name":"Steve Martinelli","email":"s.martinelli@gmail.com","username":"stevemar"},"change_message_id":"96d24c9667c36a4dc4b7b3e8af9f9707d8197c9b","unresolved":false,"context_lines":[{"line_number":146,"context_line":"        Within the request it contains BETAs authentication URL,"},{"line_number":147,"context_line":"        which was obtained out of band."},{"line_number":148,"context_line":""},{"line_number":149,"context_line":"   (B)\tCloud Implementer at BETA adds ACME as a trusted IdP via:"},{"line_number":150,"context_line":"        PUT http://BETA.COM/v3/OS-FEDERATION/identity_provider/ACME"},{"line_number":151,"context_line":"        Within the request it contains a public key that can be used"},{"line_number":152,"context_line":"        to verify signatures from ACME issued tokens."}],"source_content_type":"text/x-rst","patch_set":9,"id":"1ae5cdf2_3f9b2818","line":149,"in_reply_to":"1ae5cdf2_083726ff","updated":"2014-06-26 14:39:57.000000000","message":"Done","commit_id":"d67a84860835944fb4b733379b62fbf396800d28"},{"author":{"_account_id":8978,"name":"Marek Denis","email":"marek.denis+openstack@gmail.com","username":"marek-denis"},"change_message_id":"4d198b07fbcbe5c5fd8b5bb23c9cf395bad4e606","unresolved":false,"context_lines":[{"line_number":177,"context_line":"   The flow illustrated in Figure 2 includes the following steps:"},{"line_number":178,"context_line":""},{"line_number":179,"context_line":"   (A)  The user authenticates with their local Keystone instance, ACME,"},{"line_number":180,"context_line":"        possibly using a \u0026includeAllSPs or \u0026includeBETA query parameter."},{"line_number":181,"context_line":""},{"line_number":182,"context_line":"   (B)\tThis will allow for an extended service catalog to be returned,"},{"line_number":183,"context_line":"        which includes links to BETA\u0027s Identity service."}],"source_content_type":"text/x-rst","patch_set":9,"id":"1ae5cdf2_debed4d3","line":180,"updated":"2014-06-26 09:38:54.000000000","message":"++","commit_id":"d67a84860835944fb4b733379b62fbf396800d28"},{"author":{"_account_id":2903,"name":"Morgan Fainberg","email":"morgan.fainberg@gmail.com","username":"mdrnstm"},"change_message_id":"ebe6b6608e6dc9e7bde10cad15d3ab3e7bbfe152","unresolved":false,"context_lines":[{"line_number":179,"context_line":"   (A)  The user authenticates with their local Keystone instance, ACME,"},{"line_number":180,"context_line":"        possibly using a \u0026includeAllSPs or \u0026includeBETA query parameter."},{"line_number":181,"context_line":""},{"line_number":182,"context_line":"   (B)\tThis will allow for an extended service catalog to be returned,"},{"line_number":183,"context_line":"        which includes links to BETA\u0027s Identity service."},{"line_number":184,"context_line":""},{"line_number":185,"context_line":"   (C)  The user attempts to authenticate with BETA, via OS-FEDERATION URL"}],"source_content_type":"text/x-rst","patch_set":9,"id":"1ae5cdf2_6dc35c58","line":182,"updated":"2014-06-26 05:23:40.000000000","message":"Erroneous Tab character seems to have snuck in.","commit_id":"d67a84860835944fb4b733379b62fbf396800d28"},{"author":{"_account_id":6482,"name":"Steve Martinelli","email":"s.martinelli@gmail.com","username":"stevemar"},"change_message_id":"5cd319d5318a57a16466724ae24b11e0b5c792cc","unresolved":false,"context_lines":[{"line_number":179,"context_line":"   (A)  The user authenticates with their local Keystone instance, ACME,"},{"line_number":180,"context_line":"        possibly using a \u0026includeAllSPs or \u0026includeBETA query parameter."},{"line_number":181,"context_line":""},{"line_number":182,"context_line":"   (B)\tThis will allow for an extended service catalog to be returned,"},{"line_number":183,"context_line":"        which includes links to BETA\u0027s Identity service."},{"line_number":184,"context_line":""},{"line_number":185,"context_line":"   (C)  The user attempts to authenticate with BETA, via OS-FEDERATION URL"}],"source_content_type":"text/x-rst","patch_set":9,"id":"1ae5cdf2_6d7c3cb7","line":182,"in_reply_to":"1ae5cdf2_6dc35c58","updated":"2014-06-26 06:30:28.000000000","message":"oh thx","commit_id":"d67a84860835944fb4b733379b62fbf396800d28"},{"author":{"_account_id":2903,"name":"Morgan Fainberg","email":"morgan.fainberg@gmail.com","username":"mdrnstm"},"change_message_id":"ebe6b6608e6dc9e7bde10cad15d3ab3e7bbfe152","unresolved":false,"context_lines":[{"line_number":180,"context_line":"        possibly using a \u0026includeAllSPs or \u0026includeBETA query parameter."},{"line_number":181,"context_line":""},{"line_number":182,"context_line":"   (B)\tThis will allow for an extended service catalog to be returned,"},{"line_number":183,"context_line":"        which includes links to BETA\u0027s Identity service."},{"line_number":184,"context_line":""},{"line_number":185,"context_line":"   (C)  The user attempts to authenticate with BETA, via OS-FEDERATION URL"},{"line_number":186,"context_line":"        http://BETA.IP.COM/v3/OS-FEDERATION/identity_provider/ACME/protocol/ext-keystone/auth"}],"source_content_type":"text/x-rst","patch_set":9,"id":"1ae5cdf2_2d94f442","line":183,"updated":"2014-06-26 05:23:40.000000000","message":"++","commit_id":"d67a84860835944fb4b733379b62fbf396800d28"},{"author":{"_account_id":5956,"name":"Kristy Siu","email":"kwss@kent.ac.uk","username":"kwss"},"change_message_id":"2b1a841b4e5b436be2ead6e5fec0234e5e5c69e8","unresolved":false,"context_lines":[{"line_number":180,"context_line":"        possibly using a \u0026includeAllSPs or \u0026includeBETA query parameter."},{"line_number":181,"context_line":""},{"line_number":182,"context_line":"   (B)\tThis will allow for an extended service catalog to be returned,"},{"line_number":183,"context_line":"        which includes links to BETA\u0027s Identity service."},{"line_number":184,"context_line":""},{"line_number":185,"context_line":"   (C)  The user attempts to authenticate with BETA, via OS-FEDERATION URL"},{"line_number":186,"context_line":"        http://BETA.IP.COM/v3/OS-FEDERATION/identity_provider/ACME/protocol/ext-keystone/auth"}],"source_content_type":"text/x-rst","patch_set":9,"id":"1ae5cdf2_a9854aae","line":183,"updated":"2014-06-26 13:22:27.000000000","message":"If we are returning external SPs in the SC, is it necessary to return internal services as well? Could the user specify the target audience as internal or external (defaulting to internal to preserve normal functionality)?\n\nThis way the SC of the IdP Keystone (ACME) is never available to the SP Keystone (BETA).","commit_id":"d67a84860835944fb4b733379b62fbf396800d28"},{"author":{"_account_id":8978,"name":"Marek Denis","email":"marek.denis+openstack@gmail.com","username":"marek-denis"},"change_message_id":"4d198b07fbcbe5c5fd8b5bb23c9cf395bad4e606","unresolved":false,"context_lines":[{"line_number":180,"context_line":"        possibly using a \u0026includeAllSPs or \u0026includeBETA query parameter."},{"line_number":181,"context_line":""},{"line_number":182,"context_line":"   (B)\tThis will allow for an extended service catalog to be returned,"},{"line_number":183,"context_line":"        which includes links to BETA\u0027s Identity service."},{"line_number":184,"context_line":""},{"line_number":185,"context_line":"   (C)  The user attempts to authenticate with BETA, via OS-FEDERATION URL"},{"line_number":186,"context_line":"        http://BETA.IP.COM/v3/OS-FEDERATION/identity_provider/ACME/protocol/ext-keystone/auth"}],"source_content_type":"text/x-rst","patch_set":9,"id":"1ae5cdf2_5ecac46e","line":183,"in_reply_to":"1ae5cdf2_2d94f442","updated":"2014-06-26 09:38:54.000000000","message":"++, otherwise SC would grow too fast","commit_id":"d67a84860835944fb4b733379b62fbf396800d28"},{"author":{"_account_id":8978,"name":"Marek Denis","email":"marek.denis+openstack@gmail.com","username":"marek-denis"},"change_message_id":"8fe65c4b2026db7eb1884f78f2237cf7ebef2c83","unresolved":false,"context_lines":[{"line_number":180,"context_line":"        possibly using a \u0026includeAllSPs or \u0026includeBETA query parameter."},{"line_number":181,"context_line":""},{"line_number":182,"context_line":"   (B)\tThis will allow for an extended service catalog to be returned,"},{"line_number":183,"context_line":"        which includes links to BETA\u0027s Identity service."},{"line_number":184,"context_line":""},{"line_number":185,"context_line":"   (C)  The user attempts to authenticate with BETA, via OS-FEDERATION URL"},{"line_number":186,"context_line":"        http://BETA.IP.COM/v3/OS-FEDERATION/identity_provider/ACME/protocol/ext-keystone/auth"}],"source_content_type":"text/x-rst","patch_set":9,"id":"1ae5cdf2_7ccdbe85","line":183,"in_reply_to":"1ae5cdf2_a9854aae","updated":"2014-06-26 13:39:51.000000000","message":"Actually, if we already need to issue not-so-normal tokens this could work.","commit_id":"d67a84860835944fb4b733379b62fbf396800d28"},{"author":{"_account_id":6482,"name":"Steve Martinelli","email":"s.martinelli@gmail.com","username":"stevemar"},"change_message_id":"96d24c9667c36a4dc4b7b3e8af9f9707d8197c9b","unresolved":false,"context_lines":[{"line_number":180,"context_line":"        possibly using a \u0026includeAllSPs or \u0026includeBETA query parameter."},{"line_number":181,"context_line":""},{"line_number":182,"context_line":"   (B)\tThis will allow for an extended service catalog to be returned,"},{"line_number":183,"context_line":"        which includes links to BETA\u0027s Identity service."},{"line_number":184,"context_line":""},{"line_number":185,"context_line":"   (C)  The user attempts to authenticate with BETA, via OS-FEDERATION URL"},{"line_number":186,"context_line":"        http://BETA.IP.COM/v3/OS-FEDERATION/identity_provider/ACME/protocol/ext-keystone/auth"}],"source_content_type":"text/x-rst","patch_set":9,"id":"1ae5cdf2_dfa2443e","line":183,"in_reply_to":"1ae5cdf2_a9854aae","updated":"2014-06-26 14:39:57.000000000","message":"brilliant point. I love it. Adding it in!","commit_id":"d67a84860835944fb4b733379b62fbf396800d28"},{"author":{"_account_id":8978,"name":"Marek Denis","email":"marek.denis+openstack@gmail.com","username":"marek-denis"},"change_message_id":"4d198b07fbcbe5c5fd8b5bb23c9cf395bad4e606","unresolved":false,"context_lines":[{"line_number":187,"context_line":"        At which point a mapping associated with the protocol and IdP can"},{"line_number":188,"context_line":"        be executed via the mapping engine. The user will also have to"},{"line_number":189,"context_line":"        include a token from ACME so as to prove they are coming from a"},{"line_number":190,"context_line":"        trusted IdP."},{"line_number":191,"context_line":""},{"line_number":192,"context_line":"   (D)  Once the token is verified by checking the signature, a service"},{"line_number":193,"context_line":"        catalog can be returned that contains BETA\u0027s services."}],"source_content_type":"text/x-rst","patch_set":9,"id":"1ae5cdf2_8364f4e5","line":190,"updated":"2014-06-26 09:38:54.000000000","message":"I think this acapit is too generic. I\u0027d suggest one of the following workflow\n\n*more read-friendly version: https://www.evernote.com/shard/s107/sh/5a98433b-3e19-4f09-b70a-122472a2a363/194513837bd0162af4fcfb56a3f15357 *\n\n1) Reuse federated protocols workflow\n\nIf we want to use existing protocols like SAML/oidc and align with its original design there will be no assertion present at the point of sending HTTP request to http://BETA.IP.COM/v3/OS-FEDERATION/identity_provider/ACME/protocol/ext-keystone/auth. This means there is no way to do the mapping. We can, on the other hand, reuse existing flow, where user attempts to authenticate with BETA via OS-FEDERATION URL, gets redirected to ACME Keystone (acting as standard IdP), authenticates there, gets assertion, goes again to BETA\u0027s Keystone. Only there we have mapping, BETA Keystone issues unscoped token, the token is  scoped to BETA\u0027s project/domain and voila - we are in. But then I don\u0027t think there is a need to include ACME\u0027s token in a request to BETA. All in all, a user in order to get an assertion has to authenticate with ACME *again*. Now, I can see one possible way for dealing with *authN again* step: we reuse existing federation code in the Keystone, and put lots of the burden on keystoneclient library. But, instead of passing user/pass to ACME Keystone-IdP by client, he can prove its identity by presenting token issued by ACME. So the workflow looks like:\n\n(A) User goes to ACME, authenticates. He gets a token and extended Service Catalog\n\n(B) User goes to BETA\u0027s Keystone and initiates federated authN. BETA issues authN request, according to the protocol being used, client now needs to, again, go to ACME and in order to prove his identity he just reuses the token from (A).\n\n(C) ACME Keystone authenticates the token and issues assertion\n\n(D) Client forwards the assertion to Keystone BETA\n\n(E) We carry on with standard procedure (mapping, scoping etc)\n\nPros:\n\n- We completely reuse existing federation code at the Keystone side\n\n- We can still use mod_shib and other Apache modules\n\n- We are compatibile with protocols like SAML and don\u0027t break anything\n\n\n\nCons:\n\n- The burden is put on the keystoneclient, but most of the code will already be there (ECP plugin for SAML for instance). Regarding authN we just need to add the code for using token (or its part) to prove the identity instead of user/pass or something.\n\n- keystoneclient needs to handle multiple tokens per cloud (but this is going to happen either way, not matter how we solve this challenge)\n\n- looks like we are improving user experience just a little and add great impact and effort on the Keystone (hey, we are basically implementing IdP into Keystone).\n\n\n\n2) We can still keep compilant with SAML/OIDC workflow, well more or less.\n\nStep (A) stays. I have no issue with that at all. Now, user wants to use BETA\u0027s services. He uses BETA\u0027s URL http://BETA.IP.COM/v3/OS-FEDERATION/identity_provider/ACME/protocol/ext-keystone/auth and here indeed passes the token (or its part) to BETA\u0027s Keystone. Keystone impersonates the user and acts on behalf of him, directly contacting ACME Keystone. Normally it\u0027s the user who initiates the federated authN, asking a Service Provider for some assertion (SP must prove it\u0027s a SP being trusted by IdP). Keystone would just produce such SAML authN request and instead of returning it to the client, and hope for the client to pass it to the IdP, would init HTTP request to the ACME Keystone(being IdP), using users\u0027s token to authenticate the user. Client is here indeed unaware what\u0027s going on behind the scenes.\n\nPros:\n\n- We are more or less compilant with federated protocols workflow (external IdP should not see any difference)\n\n- Small changes in keystoneclient\n\n- Client side is indeed mostly transparent and all the communication is happening behind the scenes\n\nCons:\n\n- We cannot rely on 100% of the existing federation code, especially SAML/OIDC logic must be implemented directly in Keystone (so it can issue SAML authN request for IdP and so on and later parse the response). This may be a non trivial task to do.\n\n- We *might* open some security risks. Keystone BETA is now acting as a user. He has user\u0027s token. As long this token can be reused, Keystone BETA can impersonate the user. If we go this way, for sure, this token should not let user do anything at his local playground (ACME). This should ONLY let others authenticate in order to get assertion/clam-like object. (Here i was also thinking about some authorization code, maybe like the one in oAuth2.0, instead of full token). In other words I want ot be able to hand my neighbour keyst to my mailbox so he can get some letters, not the key to my appartment. Also, what happens if BETA gets compromised. Am I okay giving any piece of my identity to a compromised cloud?\n This should be designed with a great thoughtfulness in mind.\n\n- keystoneclient needs to handle multiple tokens per cloud (but this is going to happen either way, not matter how we solve this challenge)\n\n\n3) Hack it all, but use assertions and SAML/OIDC/other\n\nIf we decide to keep using federated protocols, but break federated authN workflow and do some hacks on top of it, we might want ACME to return saml/claims-like object in the returned token obtained in (A). But, this again is not very convenient since IdP may need to issue different parameters (or names), depending on what SP is going to consume that assertion. And we clearly want to have optin where *all* possible federated Keystones are used. One may expect E_MAIL_ADDRESS another EmAiL and so on. Not even to mention - assertion should be encrypted with SP\u0027s public key, so ACME\u0027s Keystone would have to return all possible assertions for every enabled Keystone-SP.And this is simply wrong. So I think this option is not very viable.\n\n\n\n4) Forget about SAML/OIDC\n\nThe workflow stays basically the same, but instead of issuing SAML assertions or OIDC claims, we use some JSON which may be encrypted and create our own assertions transport layer.\n\nPros:\n\n-May be easier to implement, at least at the beginning\n\n-We create a solution fitting our needs\n\n-No hacking on top of existing, not always easy, protocols (yes, I am talking to you, SAML)\n\nCons:\n\n\n-We are creating yet another protocol\n\n-We are not compilant with the \u0027external world\u0027\n\n-In the end it may be not that easy to implement robust and secure solution.","commit_id":"d67a84860835944fb4b733379b62fbf396800d28"},{"author":{"_account_id":8978,"name":"Marek Denis","email":"marek.denis+openstack@gmail.com","username":"marek-denis"},"change_message_id":"20677bb6aad7bc8b9b8f1a5af3286feb64294d25","unresolved":false,"context_lines":[{"line_number":188,"context_line":"        be executed via the mapping engine. The user will also have to"},{"line_number":189,"context_line":"        include a token from ACME so as to prove they are coming from a"},{"line_number":190,"context_line":"        trusted IdP."},{"line_number":191,"context_line":""},{"line_number":192,"context_line":"   (D)  Once the token is verified by checking the signature, a service"},{"line_number":193,"context_line":"        catalog can be returned that contains BETA\u0027s services."},{"line_number":194,"context_line":""}],"source_content_type":"text/x-rst","patch_set":9,"id":"1ae5cdf2_b76f6627","line":191,"updated":"2014-06-26 11:47:34.000000000","message":"I just rethought David Stanek\u0027s comments that were left few patches earlier. Well, I think workflow with token handed to a remote Keystone may pose some security risks if we don\u0027t make this token very much limited. So only certain operations (like authentication in order to retrieve assertion) can be carried out.  If we consider situation with CERN being federated with ProviderA (which happens to be compromised) and ProviderB. Now, when CERN user hands his token to a ProviderA, actually hackers will only be able to fetch SAML assertion. They will not be able to authenticate on ProviderB side since they would need to sign the SAML authN request with ProviderB\u0027s private key.","commit_id":"d67a84860835944fb4b733379b62fbf396800d28"},{"author":{"_account_id":6534,"name":"David Chadwick","email":"d.w.chadwick@truetrust.co.uk","username":"d-w-chadwick"},"change_message_id":"79fc82a12af6e9598122ca68f9aeee585de3ca0f","unresolved":false,"context_lines":[{"line_number":191,"context_line":""},{"line_number":192,"context_line":"   (D)  Once the token is verified by checking the signature, a service"},{"line_number":193,"context_line":"        catalog can be returned that contains BETA\u0027s services."},{"line_number":194,"context_line":""},{"line_number":195,"context_line":""},{"line_number":196,"context_line":"Alternatives"},{"line_number":197,"context_line":"------------"}],"source_content_type":"text/x-rst","patch_set":9,"id":"1ae5cdf2_8d18a8ce","line":194,"updated":"2014-06-26 05:35:31.000000000","message":"Note. We need to add another diagram showing the case where a proxy IdP GAMMA is involved in the exchange","commit_id":"d67a84860835944fb4b733379b62fbf396800d28"},{"author":{"_account_id":6534,"name":"David Chadwick","email":"d.w.chadwick@truetrust.co.uk","username":"d-w-chadwick"},"change_message_id":"79fc82a12af6e9598122ca68f9aeee585de3ca0f","unresolved":false,"context_lines":[{"line_number":209,"context_line":"however that token would be obtained through identity provider federation"},{"line_number":210,"context_line":"to enable the same set of credentials across both. The client must be smart"},{"line_number":211,"context_line":"about where the tokens work, and must be able to handle multiple tokens."},{"line_number":212,"context_line":""},{"line_number":213,"context_line":"Data Model Impact"},{"line_number":214,"context_line":"-----------------"},{"line_number":215,"context_line":""}],"source_content_type":"text/x-rst","patch_set":9,"id":"1ae5cdf2_0d45786e","line":212,"updated":"2014-06-26 05:35:31.000000000","message":"Replace the above with a fuller explanation of the possible alternatives, then we can choose which one(s) we want to implement\n\nA.)  Require the user to obtain multiple credentials in advance, one for each CSP he is going to  visit, so that he can be authorised for any CSP service he wants to use by using the correct local token.\n\nB.)  All CSP services will cater for users from any trusted IdP or proxy IdP by accepting every credential issued within the circle of trust, so regardless of the token the user has, he  can obtain the service that is provided. (This requires every service such as Swift to be altered to accept any credential, not just locally issued ones).\n\nC.)  Each CSP hosts a local token exchange service (which could be Keystone) so that when users  land at the CSP then whatever credential they currently hold can be exchanged for the local one used by the CSP\u0027s services.\n\nD.)  A new circle of trust (CoT) token service is set up which allows users to get \"international\" credentials prior to visiting remote CSPs. Users can present these CoT tokens to every CSP in the circle of trust. The CSP sends the CoT token to the CoT Service for validation, then gives the user a local credential valid for the CSP\u0027s services.\n\nEvaluation\n\n--------------\n\nA) is very undesirable as it requires client configuration or code changes each time a new CSP is trusted, and it makes the client code more complex to handle multiple tokens with different scope and varying expiration times.\n\nB) is very undersirable as it means that every OpenStack service will need to change in order to support remote users\n\nC) This is a workable model if Keystone becomes the local token exchange service. None of the CSP\u0027s services need to change. If the user hits Keystone first it will simply exchange the remote token for a local one and then redirect the user to the local services. If the user hits a service first, it can simply send every token it receives from every user to the local Keystone to validate and Keystone will send back to the service information that it can use and understand for authorisation purposes.\n\nD) This is also a workable solution. If Keystone gives users two tokens: one issued by itself that is valid for its local services, and one issued by the CoT service that is valid for all remote services in the CoT. When the user goes to a remote CSP, this now behaves as in iii) above, except that the CoT token is sent to the CoT service for validation rather than the local Keystone service, and it returns a token valid for the local CSP.","commit_id":"d67a84860835944fb4b733379b62fbf396800d28"},{"author":{"_account_id":6482,"name":"Steve Martinelli","email":"s.martinelli@gmail.com","username":"stevemar"},"change_message_id":"5cd319d5318a57a16466724ae24b11e0b5c792cc","unresolved":false,"context_lines":[{"line_number":209,"context_line":"however that token would be obtained through identity provider federation"},{"line_number":210,"context_line":"to enable the same set of credentials across both. The client must be smart"},{"line_number":211,"context_line":"about where the tokens work, and must be able to handle multiple tokens."},{"line_number":212,"context_line":""},{"line_number":213,"context_line":"Data Model Impact"},{"line_number":214,"context_line":"-----------------"},{"line_number":215,"context_line":""}],"source_content_type":"text/x-rst","patch_set":9,"id":"1ae5cdf2_4824cec5","line":212,"in_reply_to":"1ae5cdf2_0d45786e","updated":"2014-06-26 06:30:28.000000000","message":"this is 10x better than what we have, thank you. it\u0027s going in the next patch","commit_id":"d67a84860835944fb4b733379b62fbf396800d28"},{"author":{"_account_id":2903,"name":"Morgan Fainberg","email":"morgan.fainberg@gmail.com","username":"mdrnstm"},"change_message_id":"ebe6b6608e6dc9e7bde10cad15d3ab3e7bbfe152","unresolved":false,"context_lines":[{"line_number":270,"context_line":"* If the SP deletes the IdP, then the issued tokens need to be revoked, and"},{"line_number":271,"context_line":"  any new auth requests should fail."},{"line_number":272,"context_line":""},{"line_number":273,"context_line":"* If the IdP deletes the SP, then the SP should be delete the IdP as well."},{"line_number":274,"context_line":""},{"line_number":275,"context_line":"* Possible information leakage. The token could contain a catalog, roles, etc."},{"line_number":276,"context_line":"  from ACME and that information is available to BETA. Though the information"}],"source_content_type":"text/x-rst","patch_set":9,"id":"1ae5cdf2_6ded1cb8","line":273,"updated":"2014-06-26 05:23:40.000000000","message":"How is this notified? how does the SP know to delete the IDP.  Can the SP delete the IDP without the IDP deleting the SP?","commit_id":"d67a84860835944fb4b733379b62fbf396800d28"},{"author":{"_account_id":6482,"name":"Steve Martinelli","email":"s.martinelli@gmail.com","username":"stevemar"},"change_message_id":"96d24c9667c36a4dc4b7b3e8af9f9707d8197c9b","unresolved":false,"context_lines":[{"line_number":270,"context_line":"* If the SP deletes the IdP, then the issued tokens need to be revoked, and"},{"line_number":271,"context_line":"  any new auth requests should fail."},{"line_number":272,"context_line":""},{"line_number":273,"context_line":"* If the IdP deletes the SP, then the SP should be delete the IdP as well."},{"line_number":274,"context_line":""},{"line_number":275,"context_line":"* Possible information leakage. The token could contain a catalog, roles, etc."},{"line_number":276,"context_line":"  from ACME and that information is available to BETA. Though the information"}],"source_content_type":"text/x-rst","patch_set":9,"id":"1ae5cdf2_fa8e2e26","line":273,"in_reply_to":"1ae5cdf2_23224054","updated":"2014-06-26 14:39:57.000000000","message":"It sounds like you agree with the text in the spec. I\u0027ve expanded it a bit to reflect these comments.","commit_id":"d67a84860835944fb4b733379b62fbf396800d28"},{"author":{"_account_id":6482,"name":"Steve Martinelli","email":"s.martinelli@gmail.com","username":"stevemar"},"change_message_id":"5cd319d5318a57a16466724ae24b11e0b5c792cc","unresolved":false,"context_lines":[{"line_number":270,"context_line":"* If the SP deletes the IdP, then the issued tokens need to be revoked, and"},{"line_number":271,"context_line":"  any new auth requests should fail."},{"line_number":272,"context_line":""},{"line_number":273,"context_line":"* If the IdP deletes the SP, then the SP should be delete the IdP as well."},{"line_number":274,"context_line":""},{"line_number":275,"context_line":"* Possible information leakage. The token could contain a catalog, roles, etc."},{"line_number":276,"context_line":"  from ACME and that information is available to BETA. Though the information"}],"source_content_type":"text/x-rst","patch_set":9,"id":"1ae5cdf2_a8dd52df","line":273,"in_reply_to":"1ae5cdf2_6ded1cb8","updated":"2014-06-26 06:30:28.000000000","message":"I\u0027m not sure I have a good answer here, aside from out of band.","commit_id":"d67a84860835944fb4b733379b62fbf396800d28"},{"author":{"_account_id":8978,"name":"Marek Denis","email":"marek.denis+openstack@gmail.com","username":"marek-denis"},"change_message_id":"4d198b07fbcbe5c5fd8b5bb23c9cf395bad4e606","unresolved":false,"context_lines":[{"line_number":270,"context_line":"* If the SP deletes the IdP, then the issued tokens need to be revoked, and"},{"line_number":271,"context_line":"  any new auth requests should fail."},{"line_number":272,"context_line":""},{"line_number":273,"context_line":"* If the IdP deletes the SP, then the SP should be delete the IdP as well."},{"line_number":274,"context_line":""},{"line_number":275,"context_line":"* Possible information leakage. The token could contain a catalog, roles, etc."},{"line_number":276,"context_line":"  from ACME and that information is available to BETA. Though the information"}],"source_content_type":"text/x-rst","patch_set":9,"id":"1ae5cdf2_23224054","line":273,"in_reply_to":"1ae5cdf2_a8dd52df","updated":"2014-06-26 09:38:54.000000000","message":"Morgan,\n\nI don\u0027t think the notification is required here. (or such things should be done by sending emails between organisations/users). Usually such split would happen in case of security danger (a peer is compromised) or when some agreement ends (contract is due to expire or the users didn\u0027t pay). Usually a cloud provider will send few emails asking for the money before they cut off the service, right? \n\nIn case SP was removed from list of trusted SPs, the IdP  will simply not issue an assertion for that SP. AuthN process will fail. \nIn my opinion SP should be able to remove IdP from trusted IdP and the other way round. As an admin I want to be able to protect my own cloud when the other side is compromised or starts doing crazy things. Makes sense?","commit_id":"d67a84860835944fb4b733379b62fbf396800d28"},{"author":{"_account_id":2903,"name":"Morgan Fainberg","email":"morgan.fainberg@gmail.com","username":"mdrnstm"},"change_message_id":"ebe6b6608e6dc9e7bde10cad15d3ab3e7bbfe152","unresolved":false,"context_lines":[{"line_number":278,"context_line":""},{"line_number":279,"context_line":"* Does this increase the surface area of an attack if a cloud is compromised?"},{"line_number":280,"context_line":"  For example, say ACME has a partnership with BETA and GAMMA as SPs."},{"line_number":281,"context_line":"  A compromise of BETA is a Compromise of ACME and GAMMA at the token level."},{"line_number":282,"context_line":""},{"line_number":283,"context_line":""},{"line_number":284,"context_line":"Notifications Impact"}],"source_content_type":"text/x-rst","patch_set":9,"id":"1ae5cdf2_0de818b2","line":281,"updated":"2014-06-26 05:23:40.000000000","message":"How wide is this exposure? What is the actual impact, please clarify","commit_id":"d67a84860835944fb4b733379b62fbf396800d28"},{"author":{"_account_id":6482,"name":"Steve Martinelli","email":"s.martinelli@gmail.com","username":"stevemar"},"change_message_id":"5cd319d5318a57a16466724ae24b11e0b5c792cc","unresolved":false,"context_lines":[{"line_number":278,"context_line":""},{"line_number":279,"context_line":"* Does this increase the surface area of an attack if a cloud is compromised?"},{"line_number":280,"context_line":"  For example, say ACME has a partnership with BETA and GAMMA as SPs."},{"line_number":281,"context_line":"  A compromise of BETA is a Compromise of ACME and GAMMA at the token level."},{"line_number":282,"context_line":""},{"line_number":283,"context_line":""},{"line_number":284,"context_line":"Notifications Impact"}],"source_content_type":"text/x-rst","patch_set":9,"id":"1ae5cdf2_480bee2a","line":281,"in_reply_to":"1ae5cdf2_0de818b2","updated":"2014-06-26 06:30:28.000000000","message":"Not sure, dstanek brought this up, I think he was just trying to come up with scenarios. I can double check with him.","commit_id":"d67a84860835944fb4b733379b62fbf396800d28"},{"author":{"_account_id":2903,"name":"Morgan Fainberg","email":"morgan.fainberg@gmail.com","username":"mdrnstm"},"change_message_id":"ebe6b6608e6dc9e7bde10cad15d3ab3e7bbfe152","unresolved":false,"context_lines":[{"line_number":285,"context_line":"--------------------"},{"line_number":286,"context_line":""},{"line_number":287,"context_line":"* Keystone will emit (to authenticated and authorized identities), what"},{"line_number":288,"context_line":"  revocations should occur for previously issued assertions."},{"line_number":289,"context_line":""},{"line_number":290,"context_line":"* Keystone will emit (to authenticated and authorized identities), what"},{"line_number":291,"context_line":"  services are available to other trusted Keystones to scope access to."}],"source_content_type":"text/x-rst","patch_set":9,"id":"1ae5cdf2_ad2ac4e4","line":288,"updated":"2014-06-26 05:23:40.000000000","message":"CADF? Please be specific.","commit_id":"d67a84860835944fb4b733379b62fbf396800d28"},{"author":{"_account_id":8978,"name":"Marek Denis","email":"marek.denis+openstack@gmail.com","username":"marek-denis"},"change_message_id":"4d198b07fbcbe5c5fd8b5bb23c9cf395bad4e606","unresolved":false,"context_lines":[{"line_number":285,"context_line":"--------------------"},{"line_number":286,"context_line":""},{"line_number":287,"context_line":"* Keystone will emit (to authenticated and authorized identities), what"},{"line_number":288,"context_line":"  revocations should occur for previously issued assertions."},{"line_number":289,"context_line":""},{"line_number":290,"context_line":"* Keystone will emit (to authenticated and authorized identities), what"},{"line_number":291,"context_line":"  services are available to other trusted Keystones to scope access to."}],"source_content_type":"text/x-rst","patch_set":9,"id":"1ae5cdf2_23d96056","line":288,"in_reply_to":"1ae5cdf2_2daf942c","updated":"2014-06-26 09:38:54.000000000","message":"++","commit_id":"d67a84860835944fb4b733379b62fbf396800d28"},{"author":{"_account_id":6482,"name":"Steve Martinelli","email":"s.martinelli@gmail.com","username":"stevemar"},"change_message_id":"5cd319d5318a57a16466724ae24b11e0b5c792cc","unresolved":false,"context_lines":[{"line_number":285,"context_line":"--------------------"},{"line_number":286,"context_line":""},{"line_number":287,"context_line":"* Keystone will emit (to authenticated and authorized identities), what"},{"line_number":288,"context_line":"  revocations should occur for previously issued assertions."},{"line_number":289,"context_line":""},{"line_number":290,"context_line":"* Keystone will emit (to authenticated and authorized identities), what"},{"line_number":291,"context_line":"  services are available to other trusted Keystones to scope access to."}],"source_content_type":"text/x-rst","patch_set":9,"id":"1ae5cdf2_2daf942c","line":288,"in_reply_to":"1ae5cdf2_ad2ac4e4","updated":"2014-06-26 06:30:28.000000000","message":"preferably CADF","commit_id":"d67a84860835944fb4b733379b62fbf396800d28"},{"author":{"_account_id":2903,"name":"Morgan Fainberg","email":"morgan.fainberg@gmail.com","username":"mdrnstm"},"change_message_id":"ebe6b6608e6dc9e7bde10cad15d3ab3e7bbfe152","unresolved":false,"context_lines":[{"line_number":288,"context_line":"  revocations should occur for previously issued assertions."},{"line_number":289,"context_line":""},{"line_number":290,"context_line":"* Keystone will emit (to authenticated and authorized identities), what"},{"line_number":291,"context_line":"  services are available to other trusted Keystones to scope access to."},{"line_number":292,"context_line":""},{"line_number":293,"context_line":"Other End User Impact"},{"line_number":294,"context_line":"---------------------"}],"source_content_type":"text/x-rst","patch_set":9,"id":"1ae5cdf2_2d3eb429","line":291,"updated":"2014-06-26 05:23:40.000000000","message":"This is communicating over a bus between clouds? Please elaborate on what is occurring here.","commit_id":"d67a84860835944fb4b733379b62fbf396800d28"},{"author":{"_account_id":6482,"name":"Steve Martinelli","email":"s.martinelli@gmail.com","username":"stevemar"},"change_message_id":"5cd319d5318a57a16466724ae24b11e0b5c792cc","unresolved":false,"context_lines":[{"line_number":288,"context_line":"  revocations should occur for previously issued assertions."},{"line_number":289,"context_line":""},{"line_number":290,"context_line":"* Keystone will emit (to authenticated and authorized identities), what"},{"line_number":291,"context_line":"  services are available to other trusted Keystones to scope access to."},{"line_number":292,"context_line":""},{"line_number":293,"context_line":"Other End User Impact"},{"line_number":294,"context_line":"---------------------"}],"source_content_type":"text/x-rst","patch_set":9,"id":"1ae5cdf2_68734ae7","line":291,"in_reply_to":"1ae5cdf2_2d3eb429","updated":"2014-06-26 06:30:28.000000000","message":"I think this relates back to line 273. Not sure how jsavak and jorgew thought this would work. I\u0027ll ask and update the spec.","commit_id":"d67a84860835944fb4b733379b62fbf396800d28"},{"author":{"_account_id":8978,"name":"Marek Denis","email":"marek.denis+openstack@gmail.com","username":"marek-denis"},"change_message_id":"4d198b07fbcbe5c5fd8b5bb23c9cf395bad4e606","unresolved":false,"context_lines":[{"line_number":288,"context_line":"  revocations should occur for previously issued assertions."},{"line_number":289,"context_line":""},{"line_number":290,"context_line":"* Keystone will emit (to authenticated and authorized identities), what"},{"line_number":291,"context_line":"  services are available to other trusted Keystones to scope access to."},{"line_number":292,"context_line":""},{"line_number":293,"context_line":"Other End User Impact"},{"line_number":294,"context_line":"---------------------"}],"source_content_type":"text/x-rst","patch_set":9,"id":"1ae5cdf2_c346fca6","line":291,"in_reply_to":"1ae5cdf2_68734ae7","updated":"2014-06-26 09:38:54.000000000","message":"I think this was when indeed Joe and Jorge planned to list all endpoints in the *extended Service Catalog*. I have an impression that we are all more lokking forward for listing only federated keystones. Then, I think such \u0027services broadcasting\u0027 is not required. List of federated keystones can be build by fetching all registered Keystone-SPs. And this list must be configured by a man.","commit_id":"d67a84860835944fb4b733379b62fbf396800d28"},{"author":{"_account_id":6482,"name":"Steve Martinelli","email":"s.martinelli@gmail.com","username":"stevemar"},"change_message_id":"96d24c9667c36a4dc4b7b3e8af9f9707d8197c9b","unresolved":false,"context_lines":[{"line_number":288,"context_line":"  revocations should occur for previously issued assertions."},{"line_number":289,"context_line":""},{"line_number":290,"context_line":"* Keystone will emit (to authenticated and authorized identities), what"},{"line_number":291,"context_line":"  services are available to other trusted Keystones to scope access to."},{"line_number":292,"context_line":""},{"line_number":293,"context_line":"Other End User Impact"},{"line_number":294,"context_line":"---------------------"}],"source_content_type":"text/x-rst","patch_set":9,"id":"1ae5cdf2_dabc12b8","line":291,"in_reply_to":"1ae5cdf2_c346fca6","updated":"2014-06-26 14:39:57.000000000","message":"thanks for the comments, i will remove this line from the spec","commit_id":"d67a84860835944fb4b733379b62fbf396800d28"},{"author":{"_account_id":2903,"name":"Morgan Fainberg","email":"morgan.fainberg@gmail.com","username":"mdrnstm"},"change_message_id":"ebe6b6608e6dc9e7bde10cad15d3ab3e7bbfe152","unresolved":false,"context_lines":[{"line_number":293,"context_line":"Other End User Impact"},{"line_number":294,"context_line":"---------------------"},{"line_number":295,"context_line":""},{"line_number":296,"context_line":"Potentially via ECP (https://wiki.shibboleth.net/confluence/display/SHIB2/ECP)"},{"line_number":297,"context_line":""},{"line_number":298,"context_line":"Performance Impact"},{"line_number":299,"context_line":"------------------"}],"source_content_type":"text/x-rst","patch_set":9,"id":"1ae5cdf2_4d3b0038","line":296,"updated":"2014-06-26 05:23:40.000000000","message":"Woo more ECP!","commit_id":"d67a84860835944fb4b733379b62fbf396800d28"},{"author":{"_account_id":8978,"name":"Marek Denis","email":"marek.denis+openstack@gmail.com","username":"marek-denis"},"change_message_id":"4d198b07fbcbe5c5fd8b5bb23c9cf395bad4e606","unresolved":false,"context_lines":[{"line_number":293,"context_line":"Other End User Impact"},{"line_number":294,"context_line":"---------------------"},{"line_number":295,"context_line":""},{"line_number":296,"context_line":"Potentially via ECP (https://wiki.shibboleth.net/confluence/display/SHIB2/ECP)"},{"line_number":297,"context_line":""},{"line_number":298,"context_line":"Performance Impact"},{"line_number":299,"context_line":"------------------"}],"source_content_type":"text/x-rst","patch_set":9,"id":"1ae5cdf2_e3c69815","line":296,"in_reply_to":"1ae5cdf2_4d3b0038","updated":"2014-06-26 09:38:54.000000000","message":"more kittens to die :(","commit_id":"d67a84860835944fb4b733379b62fbf396800d28"},{"author":{"_account_id":2903,"name":"Morgan Fainberg","email":"morgan.fainberg@gmail.com","username":"mdrnstm"},"change_message_id":"ebe6b6608e6dc9e7bde10cad15d3ab3e7bbfe152","unresolved":false,"context_lines":[{"line_number":298,"context_line":"Performance Impact"},{"line_number":299,"context_line":"------------------"},{"line_number":300,"context_line":""},{"line_number":301,"context_line":"None"},{"line_number":302,"context_line":""},{"line_number":303,"context_line":"Other Deployer Impact"},{"line_number":304,"context_line":"---------------------"}],"source_content_type":"text/x-rst","patch_set":9,"id":"1ae5cdf2_cd1630a7","line":301,"updated":"2014-06-26 05:23:40.000000000","message":"Would there be a larger catalog, potentially more data to send/sift through, more certs to validate tokens against?","commit_id":"d67a84860835944fb4b733379b62fbf396800d28"},{"author":{"_account_id":6482,"name":"Steve Martinelli","email":"s.martinelli@gmail.com","username":"stevemar"},"change_message_id":"5cd319d5318a57a16466724ae24b11e0b5c792cc","unresolved":false,"context_lines":[{"line_number":298,"context_line":"Performance Impact"},{"line_number":299,"context_line":"------------------"},{"line_number":300,"context_line":""},{"line_number":301,"context_line":"None"},{"line_number":302,"context_line":""},{"line_number":303,"context_line":"Other Deployer Impact"},{"line_number":304,"context_line":"---------------------"}],"source_content_type":"text/x-rst","patch_set":9,"id":"1ae5cdf2_cdc0f0e2","line":301,"in_reply_to":"1ae5cdf2_cd1630a7","updated":"2014-06-26 06:30:28.000000000","message":"ohh good point... I\u0027ll add these here in the next patch","commit_id":"d67a84860835944fb4b733379b62fbf396800d28"},{"author":{"_account_id":2903,"name":"Morgan Fainberg","email":"morgan.fainberg@gmail.com","username":"mdrnstm"},"change_message_id":"ebe6b6608e6dc9e7bde10cad15d3ab3e7bbfe152","unresolved":false,"context_lines":[{"line_number":330,"context_line":"Work Items"},{"line_number":331,"context_line":"----------"},{"line_number":332,"context_line":""},{"line_number":333,"context_line":"* Define a specification for adding and maintaining service providers."},{"line_number":334,"context_line":""},{"line_number":335,"context_line":"* Define and implement a method for storing the signing keys of the external IdP."},{"line_number":336,"context_line":""}],"source_content_type":"text/x-rst","patch_set":9,"id":"1ae5cdf2_0d0d788f","line":333,"updated":"2014-06-26 05:23:40.000000000","message":"Self referential (I like it)","commit_id":"d67a84860835944fb4b733379b62fbf396800d28"},{"author":{"_account_id":2903,"name":"Morgan Fainberg","email":"morgan.fainberg@gmail.com","username":"mdrnstm"},"change_message_id":"ebe6b6608e6dc9e7bde10cad15d3ab3e7bbfe152","unresolved":false,"context_lines":[{"line_number":332,"context_line":""},{"line_number":333,"context_line":"* Define a specification for adding and maintaining service providers."},{"line_number":334,"context_line":""},{"line_number":335,"context_line":"* Define and implement a method for storing the signing keys of the external IdP."},{"line_number":336,"context_line":""},{"line_number":337,"context_line":"* Define and implement a method of validating foreign tokens."},{"line_number":338,"context_line":""}],"source_content_type":"text/x-rst","patch_set":9,"id":"1ae5cdf2_4d222002","line":335,"updated":"2014-06-26 05:23:40.000000000","message":"Barbican?","commit_id":"d67a84860835944fb4b733379b62fbf396800d28"},{"author":{"_account_id":6482,"name":"Steve Martinelli","email":"s.martinelli@gmail.com","username":"stevemar"},"change_message_id":"5cd319d5318a57a16466724ae24b11e0b5c792cc","unresolved":false,"context_lines":[{"line_number":332,"context_line":""},{"line_number":333,"context_line":"* Define a specification for adding and maintaining service providers."},{"line_number":334,"context_line":""},{"line_number":335,"context_line":"* Define and implement a method for storing the signing keys of the external IdP."},{"line_number":336,"context_line":""},{"line_number":337,"context_line":"* Define and implement a method of validating foreign tokens."},{"line_number":338,"context_line":""}],"source_content_type":"text/x-rst","patch_set":9,"id":"1ae5cdf2_8d8b48bf","line":335,"in_reply_to":"1ae5cdf2_4d222002","updated":"2014-06-26 06:30:28.000000000","message":"That was my thought. I\u0027ll add it to this sentence.","commit_id":"d67a84860835944fb4b733379b62fbf396800d28"},{"author":{"_account_id":2903,"name":"Morgan Fainberg","email":"morgan.fainberg@gmail.com","username":"mdrnstm"},"change_message_id":"ebe6b6608e6dc9e7bde10cad15d3ab3e7bbfe152","unresolved":false,"context_lines":[{"line_number":337,"context_line":"* Define and implement a method of validating foreign tokens."},{"line_number":338,"context_line":""},{"line_number":339,"context_line":"* Define and implement a method of invalidating tokens across service"},{"line_number":340,"context_line":"  providers."},{"line_number":341,"context_line":""},{"line_number":342,"context_line":""},{"line_number":343,"context_line":"Dependencies"}],"source_content_type":"text/x-rst","patch_set":9,"id":"1ae5cdf2_0d5bb886","line":340,"updated":"2014-06-26 05:23:40.000000000","message":"I\u0027m ok with approving the spec without details on the last two in it... provided we get some stronger details before we implement these parts.","commit_id":"d67a84860835944fb4b733379b62fbf396800d28"},{"author":{"_account_id":2903,"name":"Morgan Fainberg","email":"morgan.fainberg@gmail.com","username":"mdrnstm"},"change_message_id":"ebe6b6608e6dc9e7bde10cad15d3ab3e7bbfe152","unresolved":false,"context_lines":[{"line_number":352,"context_line":"* Add unit tests for the new REST APIs."},{"line_number":353,"context_line":""},{"line_number":354,"context_line":"* If possible, create tempest tests where multiple Keystone implementations"},{"line_number":355,"context_line":"  exist."},{"line_number":356,"context_line":""},{"line_number":357,"context_line":""},{"line_number":358,"context_line":"Documentation Impact"}],"source_content_type":"text/x-rst","patch_set":9,"id":"1ae5cdf2_ed0a0cd0","line":355,"updated":"2014-06-26 05:23:40.000000000","message":"I would really like to see this (even if it means running a second keystone on a separate port).","commit_id":"d67a84860835944fb4b733379b62fbf396800d28"},{"author":{"_account_id":6482,"name":"Steve Martinelli","email":"s.martinelli@gmail.com","username":"stevemar"},"change_message_id":"5cd319d5318a57a16466724ae24b11e0b5c792cc","unresolved":false,"context_lines":[{"line_number":352,"context_line":"* Add unit tests for the new REST APIs."},{"line_number":353,"context_line":""},{"line_number":354,"context_line":"* If possible, create tempest tests where multiple Keystone implementations"},{"line_number":355,"context_line":"  exist."},{"line_number":356,"context_line":""},{"line_number":357,"context_line":""},{"line_number":358,"context_line":"Documentation Impact"}],"source_content_type":"text/x-rst","patch_set":9,"id":"1ae5cdf2_a8f47255","line":355,"in_reply_to":"1ae5cdf2_ed0a0cd0","updated":"2014-06-26 06:30:28.000000000","message":"will need to wait on client work to finish up, but i really hope we can do this!","commit_id":"d67a84860835944fb4b733379b62fbf396800d28"},{"author":{"_account_id":6482,"name":"Steve Martinelli","email":"s.martinelli@gmail.com","username":"stevemar"},"change_message_id":"5b11b99a39a2fc6bb64d273fbbae694784b0d1d6","unresolved":false,"context_lines":[{"line_number":76,"context_line":"this set of roles and assign them to users accordingly."},{"line_number":77,"context_line":""},{"line_number":78,"context_line":""},{"line_number":79,"context_line":"Requirements"},{"line_number":80,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":81,"context_line":""},{"line_number":82,"context_line":"1. The solution needs to be recursive, so that if Cloud A burst to Cloud B"}],"source_content_type":"text/x-rst","patch_set":10,"id":"1ae5cdf2_f05d6fed","line":79,"updated":"2014-06-26 15:08:27.000000000","message":"@David - Adding a new Header made the tests fail - it compares titles to a template. I just made it plain text.","commit_id":"9bd6ad078216131abf4b271c56e75e93d6b434a0"},{"author":{"_account_id":6482,"name":"Steve Martinelli","email":"s.martinelli@gmail.com","username":"stevemar"},"change_message_id":"f8e40a3921ad12365e53c466307530dce908e19c","unresolved":false,"context_lines":[{"line_number":150,"context_line":"2. ACME\u0027s Keystone mentioned in the above use cases above should"},{"line_number":151,"context_line":"have knowledge of what services and endpoints BETA offers so that"},{"line_number":152,"context_line":"it could build adequate token scope across both OpenStack clouds."},{"line_number":153,"context_line":""},{"line_number":154,"context_line":"3. BETA\u0027s Keystone, acting as a trusted service provider, will get many tokens"},{"line_number":155,"context_line":"that are not within its local store. It will need to be able to decipher"},{"line_number":156,"context_line":"where the originating Keystone is from. The token can be validated if it is"}],"source_content_type":"text/x-rst","patch_set":10,"id":"1ae5cdf2_951c1d15","line":153,"updated":"2014-06-26 14:52:46.000000000","message":"Chadwick\u0027s original comment:\n\n3. Improve the way that the concept of trusted Identity Providers is handled in Keystone, to cater for gateways and proxy IdPs.\n\nThe issue of trust gets more complex if a trusted intermediary, say GAMMA, validates the identity token issued by BETA. (GAMMA could be a remote Keystone, or an Apache front end of ACME). In this case ACME will never see the token issued by BETA, but will receive the token issued by GAMMA the trusted intermediary. This means that the trusted intermediary must say in its token who the original IdP was. In this way, ACME can look at its trust rules to determine if the token from the intermediary should be accepted or not. ACME must have trust rules to say that both GAMMA and BETA are trusted, but the rules will be different. BETA will be a trusted IdP and GAMMA will be a trusted gateway or proxy IdP. (Note that a remote Keystone could be configured twice, once as a trusted gateway when its users are authenticated by a remote IdP that it trusts, and once as an IdP when Keystone has a backend LDAP holding the un/pws of its users.)\n\nThe picture here\n\nhttp://www.slideshare.net/davidwchadwick/keystone-trust\n\nshows how the trust rules should operate","commit_id":"9bd6ad078216131abf4b271c56e75e93d6b434a0"},{"author":{"_account_id":6482,"name":"Steve Martinelli","email":"s.martinelli@gmail.com","username":"stevemar"},"change_message_id":"f8e40a3921ad12365e53c466307530dce908e19c","unresolved":false,"context_lines":[{"line_number":232,"context_line":"        At which point a mapping associated with the protocol and IdP can"},{"line_number":233,"context_line":"        be executed via the mapping engine. The user will also have to"},{"line_number":234,"context_line":"        include a token from ACME so as to prove they are coming from a"},{"line_number":235,"context_line":"        trusted IdP."},{"line_number":236,"context_line":""},{"line_number":237,"context_line":"   (D)  Once the token is verified by checking the signature, a service"},{"line_number":238,"context_line":"        catalog can be returned that contains BETA\u0027s services."}],"source_content_type":"text/x-rst","patch_set":10,"id":"1ae5cdf2_158d6d31","line":235,"updated":"2014-06-26 14:52:46.000000000","message":"Marek\u0027s comment: \n\nhttps://www.evernote.com/shard/s107/sh/5a98433b-3e19-4f09-b70a-122472a2a363/194513837bd0162af4fcfb56a3f15357\n\nThis part is too generic. \n\nIf we want to use existing protocols like SAML/oidc and align with its original design there will be no assertion present at the point of sending HTTP request to http://BETA.IP.COM/v3/OS-FEDERATION/identity_provider/ACME/protocol/ext-keystone/auth. This means there is no way to do the mapping. We can, on the other hand, reuse existing flow, where user attempts to authenticate with BETA via OS-FEDERATION URL, gets redirected to ACME Keystone (acting as standard IdP), authenticates there, gets assertion, goes again to BETA\u0027s Keystone. Only there we have mapping, BETA Keystone issues unscoped token, the token is  scoped to BETA\u0027s project/domain and voila - we are in. But then I don\u0027t think there is a need to include ACME\u0027s token in a request to BETA. All in all, a user in order to get an assertion has to authenticate with ACME *again*. Now, I can see one possible way for dealing with *authN again* step: we reuse existing federation code in the Keystone, and put lots of the burden on keystoneclient library. But, instead of passing user/pass to ACME Keystone-IdP by client, he can prove its identity by presenting token issued by ACME. So the workflow looks like:\n\n(A) User goes to ACME, authenticates. He gets a token and extended Service Catalog\n\n(B) User goes to BETA\u0027s Keystone and initiates federated authN. BETA issues authN request, according to the protocol being used, client now needs to, again, go to ACME and in order to prove his identity he just reuses the token from (A).\n\n(C) ACME Keystone authenticates the token and issues assertion\n\n(D) Client forwards the assertion to Keystone BETA\n\n(E) We carry on with standard procedure (mapping, scoping etc)\n\nPros:\n\n- We completely reuse existing federation code at the Keystone side\n\n- We can still use mod_shib and other Apache modules\n\n- We are compatibile with protocols like SAML and don\u0027t break anything\n\n\n\nCons:\n\n- The burden is put on the keystoneclient, but most of the code will already be there (ECP plugin for SAML for instance). Regarding authN we just need to add the code for using token (or its part) to prove the identity instead of user/pass or something.\n\n- keystoneclient needs to handle multiple tokens per cloud (but this is going to happen either way, not matter how we solve this challenge)\n\n- looks like we are improving user experience just a little and add great impact and effort on the Keystone (hey, we are basically implementing IdP into Keystone).\n\n\n\n* We can still keep compilant with SAML/OIDC workflow, well more or less.\n\nStep (A) stays. I have no issue with that at all. Now, user wants to use BETA\u0027s services. He uses BETA\u0027s URL http://BETA.IP.COM/v3/OS-FEDERATION/identity_provider/ACME/protocol/ext-keystone/auth and here indeed passes the token (or its part) to BETA\u0027s Keystone. Keystone impersonates the user and acts on behalf of him, directly contacting ACME Keystone. Normally it\u0027s the user who initiates the federated authN, asking a Service Provider for some assertion (SP must prove it\u0027s a SP being trusted by IdP). Keystone would just produce such SAML authN request and instead of returning it to the client, and hope for the client to pass it to the IdP, would init HTTP request to the ACME Keystone(being IdP), using users\u0027s token to authenticate the user. Client is here indeed unaware what\u0027s going on behind the scenes.\n\nPros:\n\n- We are more or less compilant with federated protocols workflow (external IdP should not see any difference)\n\n- Small changes in keystoneclient\n\n- Client side is indeed mostly transparent and all the communication is happening behind the scenes\n\nCons:\n\n- We cannot rely on 100% of the existing federation code, especially SAML/OIDC logic must be implemented directly in Keystone (so it can issue SAML authN request for IdP and so on and later parse the response). This may be a non trivial task to do.\n\n- We *might* open some security risks. Keystone BETA is now acting as a user. He has user\u0027s token. As long this token can be reused, Keystone BETA can impersonate the user. If we go this way, for sure, this token should not let user do anything at his local playground (ACME). This should ONLY let others authenticate in order to get assertion/clam-like object. (Here i was also thinking about some authorization code, maybe like the one in oAuth2.0, instead of full token). In other words I want ot be able to hand my neighbour keyst to my mailbox so he can get some letters, not the key to my appartment. This should be designed with a great thoughtfulness in mind.\n\n- keystoneclient needs to handle multiple tokens per cloud (but this is going to happen either way, not matter how we solve this challenge)\n\n\n\n* Hack it all, but use assertions\n\nIf we decide to keep using federated protocols, but break federated authN workflow and do some hacks on top of it, we might want ACME to return saml/claims-like object in the returned token obtained in (A). But, this again is not very convenient since IdP may need to issue different parameters (or names), depending on what SP is going to consume that assertion. And we clearly want to have optin where *all* possible federated Keystones are used. One may expect E_MAIL_ADDRESS another EmAiL and so on. Not even to mention - assertion should be encrypted with SP\u0027s public key, so ACME\u0027s Keystone would have to return all possible assertions for every enabled Keystone-SP.And this is simply wrong. So I think this option is not very viable.\n\n\n\n* Forget about SAML/OIDC\n\nThe workflow stays basically the same, but instead of issuing SAML assertions or OIDC claims, we use some JSON which may be encrypted and create our own assertions transport layer.\n\nPros:\n\nMay be easier to implement, at least at the beginning\n\nWe create a solution fitting our needs\n\nNo hacking on top of existing, not always easy, protocols (yes, I am talking to you, SAML)\n\nCons:\n\n\nWe are creating yet another protocol\n\nWe are not compilant with \u0027external world\u0027\n\nIn the end it may be not that easy to implement robust and secure solution.","commit_id":"9bd6ad078216131abf4b271c56e75e93d6b434a0"},{"author":{"_account_id":6482,"name":"Steve Martinelli","email":"s.martinelli@gmail.com","username":"stevemar"},"change_message_id":"f8e40a3921ad12365e53c466307530dce908e19c","unresolved":false,"context_lines":[{"line_number":236,"context_line":""},{"line_number":237,"context_line":"   (D)  Once the token is verified by checking the signature, a service"},{"line_number":238,"context_line":"        catalog can be returned that contains BETA\u0027s services."},{"line_number":239,"context_line":""},{"line_number":240,"context_line":""},{"line_number":241,"context_line":"Alternatives"},{"line_number":242,"context_line":"------------"}],"source_content_type":"text/x-rst","patch_set":10,"id":"1ae5cdf2_75e6b117","line":239,"updated":"2014-06-26 14:52:46.000000000","message":"Chadwick:\n\nNote. We need to add another diagram showing the case where a proxy IdP GAMMA is involved in the exchange","commit_id":"9bd6ad078216131abf4b271c56e75e93d6b434a0"},{"author":{"_account_id":11022,"name":"Rodrigo Duarte Sousa","email":"rodrigodsousa@gmail.com","username":"rodrigods"},"change_message_id":"0ca4779a08f621760b22080169d213ebbb4b5d14","unresolved":false,"context_lines":[{"line_number":24,"context_line":"  an OpenStack cloud."},{"line_number":25,"context_line":""},{"line_number":26,"context_line":"* Service Provider (SP) - An entity that offers an OpenStack compatible"},{"line_number":27,"context_line":"  public cloud service (public or private)."},{"line_number":28,"context_line":""},{"line_number":29,"context_line":"* Identity provider (IdP) - The federated identity provider of the end user."},{"line_number":30,"context_line":"  The service responsible for managing the authentication of the end user."}],"source_content_type":"text/x-rst","patch_set":11,"id":"1ae5cdf2_1009fb94","line":27,"updated":"2014-06-26 15:12:35.000000000","message":"I think you mean \"cloud service (public or private)\" without the \"public\" upfront","commit_id":"cb7fc464e24f52bdc3a4714cadb4a9a3909005b9"},{"author":{"_account_id":6482,"name":"Steve Martinelli","email":"s.martinelli@gmail.com","username":"stevemar"},"change_message_id":"fd2d6463894af111b20364bbc0b23498dd0c3a29","unresolved":false,"context_lines":[{"line_number":24,"context_line":"  an OpenStack cloud."},{"line_number":25,"context_line":""},{"line_number":26,"context_line":"* Service Provider (SP) - An entity that offers an OpenStack compatible"},{"line_number":27,"context_line":"  public cloud service (public or private)."},{"line_number":28,"context_line":""},{"line_number":29,"context_line":"* Identity provider (IdP) - The federated identity provider of the end user."},{"line_number":30,"context_line":"  The service responsible for managing the authentication of the end user."}],"source_content_type":"text/x-rst","patch_set":11,"id":"1ae5cdf2_d0ddd3de","line":27,"in_reply_to":"1ae5cdf2_1009fb94","updated":"2014-06-26 15:16:42.000000000","message":"thx for the catch","commit_id":"cb7fc464e24f52bdc3a4714cadb4a9a3909005b9"},{"author":{"_account_id":6534,"name":"David Chadwick","email":"d.w.chadwick@truetrust.co.uk","username":"d-w-chadwick"},"change_message_id":"f47ab269a8b0490003b4956ec1eba5db2a283899","unresolved":false,"context_lines":[{"line_number":77,"context_line":"1. The solution needs to be recursive, so that if Cloud A burst to Cloud B"},{"line_number":78,"context_line":"when it is overloaded, and Cloud B burst to Cloud C when it is overloaded,"},{"line_number":79,"context_line":"then jobs from A can be burst to C via B."},{"line_number":80,"context_line":""},{"line_number":81,"context_line":"2. The solution needs to require minimum changes to existing non-Keystone"},{"line_number":82,"context_line":"components, i.e., both clients and OpenStack services, or to put it another"},{"line_number":83,"context_line":"way, the majority of the changes should be applied to Keystone."}],"source_content_type":"text/x-rst","patch_set":11,"id":"1ae5cdf2_d56dae04","line":80,"updated":"2014-06-27 05:16:22.000000000","message":"Q from Craig.\n\nWho is doing the cloud-bursting?  Is a\nCloud A User explicitly cloud-bursting to Cloud B, or is Cloud A\ntransparently cloud-bursting to Cloud B on behalf (and unbeknownst) to\nthe Cloud A User?  In this latter case, it seems that the Nova\nScheduler would have to know when and how to do this cloud-bursting\n(assuming that only compute resources are required).","commit_id":"cb7fc464e24f52bdc3a4714cadb4a9a3909005b9"},{"author":{"_account_id":5956,"name":"Kristy Siu","email":"kwss@kent.ac.uk","username":"kwss"},"change_message_id":"8f552c75c3d756e066f9e5652e8c0d66f9fec91c","unresolved":false,"context_lines":[{"line_number":101,"context_line":"5. The solution must not reduce the functionality of existing clients and"},{"line_number":102,"context_line":"services."},{"line_number":103,"context_line":""},{"line_number":104,"context_line":"6. The solution must work for bother federated users and non-federated"},{"line_number":105,"context_line":"users."},{"line_number":106,"context_line":""},{"line_number":107,"context_line":"7. The solution should not unduly impact on the non-functional aspects of"}],"source_content_type":"text/x-rst","patch_set":11,"id":"1ae5cdf2_abe29a2d","line":104,"updated":"2014-06-26 15:29:24.000000000","message":"both*","commit_id":"cb7fc464e24f52bdc3a4714cadb4a9a3909005b9"},{"author":{"_account_id":6482,"name":"Steve Martinelli","email":"s.martinelli@gmail.com","username":"stevemar"},"change_message_id":"9b80a05754249c26f8b66a16bb99a56478715f7a","unresolved":false,"context_lines":[{"line_number":101,"context_line":"5. The solution must not reduce the functionality of existing clients and"},{"line_number":102,"context_line":"services."},{"line_number":103,"context_line":""},{"line_number":104,"context_line":"6. The solution must work for bother federated users and non-federated"},{"line_number":105,"context_line":"users."},{"line_number":106,"context_line":""},{"line_number":107,"context_line":"7. The solution should not unduly impact on the non-functional aspects of"}],"source_content_type":"text/x-rst","patch_set":11,"id":"1ae5cdf2_23886e6a","line":104,"in_reply_to":"1ae5cdf2_abe29a2d","updated":"2014-06-26 17:31:34.000000000","message":"oops yes.","commit_id":"cb7fc464e24f52bdc3a4714cadb4a9a3909005b9"},{"author":{"_account_id":11022,"name":"Rodrigo Duarte Sousa","email":"rodrigodsousa@gmail.com","username":"rodrigods"},"change_message_id":"0ca4779a08f621760b22080169d213ebbb4b5d14","unresolved":false,"context_lines":[{"line_number":142,"context_line":"should be considered to be a repeat of the above, only in the opposite"},{"line_number":143,"context_line":"direction."},{"line_number":144,"context_line":""},{"line_number":145,"context_line":"2. ACME\u0027s Keystone mentioned in the above use cases above should"},{"line_number":146,"context_line":"have knowledge of what services and endpoints BETA offers so that"},{"line_number":147,"context_line":"it could build adequate token scope across both OpenStack clouds."},{"line_number":148,"context_line":""}],"source_content_type":"text/x-rst","patch_set":11,"id":"1ae5cdf2_50e8e3b2","line":145,"updated":"2014-06-26 15:12:35.000000000","message":"nit: \"above use cases above\"","commit_id":"cb7fc464e24f52bdc3a4714cadb4a9a3909005b9"},{"author":{"_account_id":6482,"name":"Steve Martinelli","email":"s.martinelli@gmail.com","username":"stevemar"},"change_message_id":"fd2d6463894af111b20364bbc0b23498dd0c3a29","unresolved":false,"context_lines":[{"line_number":142,"context_line":"should be considered to be a repeat of the above, only in the opposite"},{"line_number":143,"context_line":"direction."},{"line_number":144,"context_line":""},{"line_number":145,"context_line":"2. ACME\u0027s Keystone mentioned in the above use cases above should"},{"line_number":146,"context_line":"have knowledge of what services and endpoints BETA offers so that"},{"line_number":147,"context_line":"it could build adequate token scope across both OpenStack clouds."},{"line_number":148,"context_line":""}],"source_content_type":"text/x-rst","patch_set":11,"id":"1ae5cdf2_f0ed6f8f","line":145,"in_reply_to":"1ae5cdf2_50e8e3b2","updated":"2014-06-26 15:16:42.000000000","message":"thx for the catch","commit_id":"cb7fc464e24f52bdc3a4714cadb4a9a3909005b9"},{"author":{"_account_id":6482,"name":"Steve Martinelli","email":"s.martinelli@gmail.com","username":"stevemar"},"change_message_id":"78e64bea9788e1ac436f5be59e1227c1987d8c8c","unresolved":false,"context_lines":[{"line_number":145,"context_line":"2. ACME\u0027s Keystone mentioned in the above use cases above should"},{"line_number":146,"context_line":"have knowledge of what services and endpoints BETA offers so that"},{"line_number":147,"context_line":"it could build adequate token scope across both OpenStack clouds."},{"line_number":148,"context_line":""},{"line_number":149,"context_line":"3. BETA\u0027s Keystone, acting as a trusted service provider, will get many tokens"},{"line_number":150,"context_line":"that are not within its local store. It will need to be able to decipher"},{"line_number":151,"context_line":"where the originating Keystone is from. The token can be validated if it is"}],"source_content_type":"text/x-rst","patch_set":11,"id":"1ae5cdf2_70715f76","line":148,"updated":"2014-06-26 15:08:32.000000000","message":"Chadwick\u0027s original comment:\n\n3. Improve the way that the concept of trusted Identity Providers is handled in Keystone, to cater for gateways and proxy IdPs.\n\nThe issue of trust gets more complex if a trusted intermediary, say GAMMA, validates the identity token issued by BETA. (GAMMA could be a remote Keystone, or an Apache front end of ACME). In this case ACME will never see the token issued by BETA, but will receive the token issued by GAMMA the trusted intermediary. This means that the trusted intermediary must say in its token who the original IdP was. In this way, ACME can look at its trust rules to determine if the token from the intermediary should be accepted or not. ACME must have trust rules to say that both GAMMA and BETA are trusted, but the rules will be different. BETA will be a trusted IdP and GAMMA will be a trusted gateway or proxy IdP. (Note that a remote Keystone could be configured twice, once as a trusted gateway when its users are authenticated by a remote IdP that it trusts, and once as an IdP when Keystone has a backend LDAP holding the un/pws of its users.)\n\nThe picture here\n\nhttp://www.slideshare.net/davidwchadwick/keystone-trust\n\nshows how the trust rules should operate","commit_id":"cb7fc464e24f52bdc3a4714cadb4a9a3909005b9"},{"author":{"_account_id":6534,"name":"David Chadwick","email":"d.w.chadwick@truetrust.co.uk","username":"d-w-chadwick"},"change_message_id":"f47ab269a8b0490003b4956ec1eba5db2a283899","unresolved":false,"context_lines":[{"line_number":167,"context_line":"     |          |                                 |               |"},{"line_number":168,"context_line":"     +----------+                                 +---------------+"},{"line_number":169,"context_line":"                                                      |"},{"line_number":170,"context_line":"                                                      | Out of Band"},{"line_number":171,"context_line":"                                                      |"},{"line_number":172,"context_line":"     +----------+                                 +---------------+"},{"line_number":173,"context_line":"     |          |\u003c---(B)-- Add ACME as an IdP ----|               |"}],"source_content_type":"text/x-rst","patch_set":11,"id":"1ae5cdf2_50dfec65","line":170,"updated":"2014-06-27 05:16:22.000000000","message":"Add  Step Z.  to ACME to show that user may authenticate to ACME via federation and not directly via un/pw login\n\n\u003c---- (Z) Add IdP 1 as an IdP  ---- Cloud Implementor","commit_id":"cb7fc464e24f52bdc3a4714cadb4a9a3909005b9"},{"author":{"_account_id":6482,"name":"Steve Martinelli","email":"s.martinelli@gmail.com","username":"stevemar"},"change_message_id":"9bca58cd0352343d76356b106af8ac1e281344bc","unresolved":false,"context_lines":[{"line_number":167,"context_line":"     |          |                                 |               |"},{"line_number":168,"context_line":"     +----------+                                 +---------------+"},{"line_number":169,"context_line":"                                                      |"},{"line_number":170,"context_line":"                                                      | Out of Band"},{"line_number":171,"context_line":"                                                      |"},{"line_number":172,"context_line":"     +----------+                                 +---------------+"},{"line_number":173,"context_line":"     |          |\u003c---(B)-- Add ACME as an IdP ----|               |"}],"source_content_type":"text/x-rst","patch_set":11,"id":"1ae5cdf2_10fe4438","line":170,"in_reply_to":"1ae5cdf2_50dfec65","updated":"2014-06-27 05:54:54.000000000","message":"Done","commit_id":"cb7fc464e24f52bdc3a4714cadb4a9a3909005b9"},{"author":{"_account_id":6534,"name":"David Chadwick","email":"d.w.chadwick@truetrust.co.uk","username":"d-w-chadwick"},"change_message_id":"f47ab269a8b0490003b4956ec1eba5db2a283899","unresolved":false,"context_lines":[{"line_number":175,"context_line":"     |          |                                 |  Implementer  |"},{"line_number":176,"context_line":"     |          |                                 |               |"},{"line_number":177,"context_line":"     +----------+                                 +---------------+"},{"line_number":178,"context_line":""},{"line_number":179,"context_line":"   The flow illustrated in Figure 1 includes the following steps:"},{"line_number":180,"context_line":""},{"line_number":181,"context_line":"   (A)  Cloud Implementer at ACME adds BETA as a trusted SP via:"}],"source_content_type":"text/x-rst","patch_set":11,"id":"1ae5cdf2_35017207","line":178,"updated":"2014-06-27 05:16:22.000000000","message":"Below this we should have the following to show how recursiveness can work\n\nto BETA    \u003c-------------- (C) Add DELTA as an SP ----------  Cloud Implementor\n\n-------------------+\n\nDELTA       |             \u003c ---------- (D) Add BETA as an IDP -------Cloud Implementor\n\n\n-------------------+","commit_id":"cb7fc464e24f52bdc3a4714cadb4a9a3909005b9"},{"author":{"_account_id":6482,"name":"Steve Martinelli","email":"s.martinelli@gmail.com","username":"stevemar"},"change_message_id":"9bca58cd0352343d76356b106af8ac1e281344bc","unresolved":false,"context_lines":[{"line_number":175,"context_line":"     |          |                                 |  Implementer  |"},{"line_number":176,"context_line":"     |          |                                 |               |"},{"line_number":177,"context_line":"     +----------+                                 +---------------+"},{"line_number":178,"context_line":""},{"line_number":179,"context_line":"   The flow illustrated in Figure 1 includes the following steps:"},{"line_number":180,"context_line":""},{"line_number":181,"context_line":"   (A)  Cloud Implementer at ACME adds BETA as a trusted SP via:"}],"source_content_type":"text/x-rst","patch_set":11,"id":"1ae5cdf2_5079acc3","line":178,"in_reply_to":"1ae5cdf2_35017207","updated":"2014-06-27 05:54:54.000000000","message":"Done","commit_id":"cb7fc464e24f52bdc3a4714cadb4a9a3909005b9"},{"author":{"_account_id":6534,"name":"David Chadwick","email":"d.w.chadwick@truetrust.co.uk","username":"d-w-chadwick"},"change_message_id":"f47ab269a8b0490003b4956ec1eba5db2a283899","unresolved":false,"context_lines":[{"line_number":176,"context_line":"     |          |                                 |               |"},{"line_number":177,"context_line":"     +----------+                                 +---------------+"},{"line_number":178,"context_line":""},{"line_number":179,"context_line":"   The flow illustrated in Figure 1 includes the following steps:"},{"line_number":180,"context_line":""},{"line_number":181,"context_line":"   (A)  Cloud Implementer at ACME adds BETA as a trusted SP via:"},{"line_number":182,"context_line":"        PUT http://ACME.COM/v3/OS-FEDERATION/service_providers/BETA"}],"source_content_type":"text/x-rst","patch_set":11,"id":"1ae5cdf2_70cf88b3","line":179,"updated":"2014-06-27 05:16:22.000000000","message":"(Z)  Cloud Implementer at ACME adds IdP 1 as a trusted IdP etc.","commit_id":"cb7fc464e24f52bdc3a4714cadb4a9a3909005b9"},{"author":{"_account_id":6482,"name":"Steve Martinelli","email":"s.martinelli@gmail.com","username":"stevemar"},"change_message_id":"9bca58cd0352343d76356b106af8ac1e281344bc","unresolved":false,"context_lines":[{"line_number":176,"context_line":"     |          |                                 |               |"},{"line_number":177,"context_line":"     +----------+                                 +---------------+"},{"line_number":178,"context_line":""},{"line_number":179,"context_line":"   The flow illustrated in Figure 1 includes the following steps:"},{"line_number":180,"context_line":""},{"line_number":181,"context_line":"   (A)  Cloud Implementer at ACME adds BETA as a trusted SP via:"},{"line_number":182,"context_line":"        PUT http://ACME.COM/v3/OS-FEDERATION/service_providers/BETA"}],"source_content_type":"text/x-rst","patch_set":11,"id":"1ae5cdf2_f05c784e","line":179,"in_reply_to":"1ae5cdf2_70cf88b3","updated":"2014-06-27 05:54:54.000000000","message":"Done","commit_id":"cb7fc464e24f52bdc3a4714cadb4a9a3909005b9"},{"author":{"_account_id":6534,"name":"David Chadwick","email":"d.w.chadwick@truetrust.co.uk","username":"d-w-chadwick"},"change_message_id":"f47ab269a8b0490003b4956ec1eba5db2a283899","unresolved":false,"context_lines":[{"line_number":189,"context_line":"        to verify signatures from ACME issued tokens."},{"line_number":190,"context_line":"        The Cloud Implementer must also create a Mapping and associate"},{"line_number":191,"context_line":"        the mapping with ACME IdP and a protocol."},{"line_number":192,"context_line":""},{"line_number":193,"context_line":""},{"line_number":194,"context_line":"::"},{"line_number":195,"context_line":""}],"source_content_type":"text/x-rst","patch_set":11,"id":"1ae5cdf2_b052f00f","line":192,"updated":"2014-06-27 05:16:22.000000000","message":"(C) Cloud Implementor at BETA adds DELTA as a trusted SP etc.\n\n (D) Cloud Implementor at DELTA adds BETA as a trusted IdP etc.","commit_id":"cb7fc464e24f52bdc3a4714cadb4a9a3909005b9"},{"author":{"_account_id":6482,"name":"Steve Martinelli","email":"s.martinelli@gmail.com","username":"stevemar"},"change_message_id":"9bca58cd0352343d76356b106af8ac1e281344bc","unresolved":false,"context_lines":[{"line_number":189,"context_line":"        to verify signatures from ACME issued tokens."},{"line_number":190,"context_line":"        The Cloud Implementer must also create a Mapping and associate"},{"line_number":191,"context_line":"        the mapping with ACME IdP and a protocol."},{"line_number":192,"context_line":""},{"line_number":193,"context_line":""},{"line_number":194,"context_line":"::"},{"line_number":195,"context_line":""}],"source_content_type":"text/x-rst","patch_set":11,"id":"1ae5cdf2_9035f4f8","line":192,"in_reply_to":"1ae5cdf2_b052f00f","updated":"2014-06-27 05:54:54.000000000","message":"Done","commit_id":"cb7fc464e24f52bdc3a4714cadb4a9a3909005b9"},{"author":{"_account_id":6534,"name":"David Chadwick","email":"d.w.chadwick@truetrust.co.uk","username":"d-w-chadwick"},"change_message_id":"f47ab269a8b0490003b4956ec1eba5db2a283899","unresolved":false,"context_lines":[{"line_number":201,"context_line":"     |          |----(B)--  Catalog returned  ---\u003e|               |"},{"line_number":202,"context_line":"     +----------+                                 +---------------+"},{"line_number":203,"context_line":"                                                      |      ^"},{"line_number":204,"context_line":"                                                      |      |"},{"line_number":205,"context_line":"                                                      |      |"},{"line_number":206,"context_line":"                                                      |      |"},{"line_number":207,"context_line":"     +---------+                                      |      |"}],"source_content_type":"text/x-rst","patch_set":11,"id":"1ae5cdf2_903b349b","line":204,"updated":"2014-06-27 05:16:22.000000000","message":"In fact, User will not authenticate directly to ACME, but will authenticate to his local IdP, IdP 1.  So this diagram should be updated to show what actually happens, i.e. that user authenticates to IdP 1 and gains access to ACME as a result. This shows the recursive nature of the work we are doing.","commit_id":"cb7fc464e24f52bdc3a4714cadb4a9a3909005b9"},{"author":{"_account_id":6482,"name":"Steve Martinelli","email":"s.martinelli@gmail.com","username":"stevemar"},"change_message_id":"9bca58cd0352343d76356b106af8ac1e281344bc","unresolved":false,"context_lines":[{"line_number":201,"context_line":"     |          |----(B)--  Catalog returned  ---\u003e|               |"},{"line_number":202,"context_line":"     +----------+                                 +---------------+"},{"line_number":203,"context_line":"                                                      |      ^"},{"line_number":204,"context_line":"                                                      |      |"},{"line_number":205,"context_line":"                                                      |      |"},{"line_number":206,"context_line":"                                                      |      |"},{"line_number":207,"context_line":"     +---------+                                      |      |"}],"source_content_type":"text/x-rst","patch_set":11,"id":"1ae5cdf2_7b04c9c5","line":204,"in_reply_to":"1ae5cdf2_903b349b","updated":"2014-06-27 05:54:54.000000000","message":"Done","commit_id":"cb7fc464e24f52bdc3a4714cadb4a9a3909005b9"},{"author":{"_account_id":6534,"name":"David Chadwick","email":"d.w.chadwick@truetrust.co.uk","username":"d-w-chadwick"},"change_message_id":"f47ab269a8b0490003b4956ec1eba5db2a283899","unresolved":false,"context_lines":[{"line_number":215,"context_line":""},{"line_number":216,"context_line":"   (A)  The user authenticates with their local Keystone instance, ACME,"},{"line_number":217,"context_line":"        possibly using a \u0026includeAllSPs or \u0026includeBETA query parameter."},{"line_number":218,"context_line":""},{"line_number":219,"context_line":"   (B)  This will allow for an extended service catalog to be returned,"},{"line_number":220,"context_line":"        which includes links to BETA\u0027s Identity service. Additionally,"},{"line_number":221,"context_line":"        this service catalog does not necessarily need to contain any"}],"source_content_type":"text/x-rst","patch_set":11,"id":"1ae5cdf2_30fee0af","line":218,"updated":"2014-06-27 05:16:22.000000000","message":"(A) the user authenticates to their local Keystone instance, ACME, using their local IdP 1. One can see that the \u0026include parameter is nothing to do with the authentication phase, as IdP 1 knows nothing about this parameter. Rather, the \u0026include parameter is to do with service provision and is a parameter associated with the SP  AFTER AUTHENTICATION has taken place. ie. it is feature of the request to the SP and is to do with authorisation.","commit_id":"cb7fc464e24f52bdc3a4714cadb4a9a3909005b9"},{"author":{"_account_id":6482,"name":"Steve Martinelli","email":"s.martinelli@gmail.com","username":"stevemar"},"change_message_id":"9bca58cd0352343d76356b106af8ac1e281344bc","unresolved":false,"context_lines":[{"line_number":215,"context_line":""},{"line_number":216,"context_line":"   (A)  The user authenticates with their local Keystone instance, ACME,"},{"line_number":217,"context_line":"        possibly using a \u0026includeAllSPs or \u0026includeBETA query parameter."},{"line_number":218,"context_line":""},{"line_number":219,"context_line":"   (B)  This will allow for an extended service catalog to be returned,"},{"line_number":220,"context_line":"        which includes links to BETA\u0027s Identity service. Additionally,"},{"line_number":221,"context_line":"        this service catalog does not necessarily need to contain any"}],"source_content_type":"text/x-rst","patch_set":11,"id":"1ae5cdf2_3b67a1b9","line":218,"in_reply_to":"1ae5cdf2_30fee0af","updated":"2014-06-27 05:54:54.000000000","message":"Done","commit_id":"cb7fc464e24f52bdc3a4714cadb4a9a3909005b9"},{"author":{"_account_id":6482,"name":"Steve Martinelli","email":"s.martinelli@gmail.com","username":"stevemar"},"change_message_id":"78e64bea9788e1ac436f5be59e1227c1987d8c8c","unresolved":false,"context_lines":[{"line_number":227,"context_line":"        At which point a mapping associated with the protocol and IdP can"},{"line_number":228,"context_line":"        be executed via the mapping engine. The user will also have to"},{"line_number":229,"context_line":"        include a token from ACME so as to prove they are coming from a"},{"line_number":230,"context_line":"        trusted IdP."},{"line_number":231,"context_line":""},{"line_number":232,"context_line":"   (D)  Once the token is verified by checking the signature, a service"},{"line_number":233,"context_line":"        catalog can be returned that contains BETA\u0027s services."}],"source_content_type":"text/x-rst","patch_set":11,"id":"1ae5cdf2_901c2b15","line":230,"updated":"2014-06-26 15:08:32.000000000","message":"Marek\u0027s original comment:\n\nhttps://www.evernote.com/shard/s107/sh/5a98433b-3e19-4f09-b70a-122472a2a363/194513837bd0162af4fcfb56a3f15357\n\nReuse federated protocols workflow\n\nIf we want to use existing protocols like SAML/oidc and align with its original design there will be no assertion present at the point of sending HTTP request to http://BETA.IP.COM/v3/OS-FEDERATION/identity_provider/ACME/protocol/ext-keystone/auth. This means there is no way to do the mapping. We can, on the other hand, reuse existing flow, where user attempts to authenticate with BETA via OS-FEDERATION URL, gets redirected to ACME Keystone (acting as standard IdP), authenticates there, gets assertion, goes again to BETA\u0027s Keystone. Only there we have mapping, BETA Keystone issues unscoped token, the token is  scoped to BETA\u0027s project/domain and voila - we are in. But then I don\u0027t think there is a need to include ACME\u0027s token in a request to BETA. All in all, a user in order to get an assertion has to authenticate with ACME *again*. Now, I can see one possible way for dealing with *authN again* step: we reuse existing federation code in the Keystone, and put lots of the burden on keystoneclient library. But, instead of passing user/pass to ACME Keystone-IdP by client, he can prove its identity by presenting token issued by ACME. So the workflow looks like:\n\n(A) User goes to ACME, authenticates. He gets a token and extended Service Catalog\n\n(B) User goes to BETA\u0027s Keystone and initiates federated authN. BETA issues authN request, according to the protocol being used, client now needs to, again, go to ACME and in order to prove his identity he just reuses the token from (A).\n\n(C) ACME Keystone authenticates the token and issues assertion\n\n(D) Client forwards the assertion to Keystone BETA\n\n(E) We carry on with standard procedure (mapping, scoping etc)\n\nPros:\n\n- We completely reuse existing federation code at the Keystone side\n\n- We can still use mod_shib and other Apache modules\n\n- We are compatibile with protocols like SAML and don\u0027t break anything\n\n\n\nCons:\n\n- The burden is put on the keystoneclient, but most of the code will already be there (ECP plugin for SAML for instance). Regarding authN we just need to add the code for using token (or its part) to prove the identity instead of user/pass or something.\n\n- keystoneclient needs to handle multiple tokens per cloud (but this is going to happen either way, not matter how we solve this challenge)\n\n- looks like we are improving user experience just a little and add great impact and effort on the Keystone (hey, we are basically implementing IdP into Keystone).\n\n\n\n* We can still keep compilant with SAML/OIDC workflow, well more or less.\n\nStep (A) stays. I have no issue with that at all. Now, user wants to use BETA\u0027s services. He uses BETA\u0027s URL http://BETA.IP.COM/v3/OS-FEDERATION/identity_provider/ACME/protocol/ext-keystone/auth and here indeed passes the token (or its part) to BETA\u0027s Keystone. Keystone impersonates the user and acts on behalf of him, directly contacting ACME Keystone. Normally it\u0027s the user who initiates the federated authN, asking a Service Provider for some assertion (SP must prove it\u0027s a SP being trusted by IdP). Keystone would just produce such SAML authN request and instead of returning it to the client, and hope for the client to pass it to the IdP, would init HTTP request to the ACME Keystone(being IdP), using users\u0027s token to authenticate the user. Client is here indeed unaware what\u0027s going on behind the scenes.\n\nPros:\n\n- We are more or less compilant with federated protocols workflow (external IdP should not see any difference)\n\n- Small changes in keystoneclient\n\n- Client side is indeed mostly transparent and all the communication is happening behind the scenes\n\nCons:\n\n- We cannot rely on 100% of the existing federation code, especially SAML/OIDC logic must be implemented directly in Keystone (so it can issue SAML authN request for IdP and so on and later parse the response). This may be a non trivial task to do.\n\n- We *might* open some security risks. Keystone BETA is now acting as a user. He has user\u0027s token. As long this token can be reused, Keystone BETA can impersonate the user. If we go this way, for sure, this token should not let user do anything at his local playground (ACME). This should ONLY let others authenticate in order to get assertion/clam-like object. (Here i was also thinking about some authorization code, maybe like the one in oAuth2.0, instead of full token). In other words I want ot be able to hand my neighbour keyst to my mailbox so he can get some letters, not the key to my appartment. This should be designed with a great thoughtfulness in mind.\n\n- keystoneclient needs to handle multiple tokens per cloud (but this is going to happen either way, not matter how we solve this challenge)\n\n\n\n* Hack it all, but use assertions\n\nIf we decide to keep using federated protocols, but break federated authN workflow and do some hacks on top of it, we might want ACME to return saml/claims-like object in the returned token obtained in (A). But, this again is not very convenient since IdP may need to issue different parameters (or names), depending on what SP is going to consume that assertion. And we clearly want to have optin where *all* possible federated Keystones are used. One may expect E_MAIL_ADDRESS another EmAiL and so on. Not even to mention - assertion should be encrypted with SP\u0027s public key, so ACME\u0027s Keystone would have to return all possible assertions for every enabled Keystone-SP.And this is simply wrong. So I think this option is not very viable.\n\n\n\n* Forget about SAML/OIDC\n\nThe workflow stays basically the same, but instead of issuing SAML assertions or OIDC claims, we use some JSON which may be encrypted and create our own assertions transport layer.\n\nPros:\n\nMay be easier to implement, at least at the beginning\n\nWe create a solution fitting our needs\n\nNo hacking on top of existing, not always easy, protocols (yes, I am talking to you, SAML)\n\nCons:\n\nWe are creating yet another protocol\n\nWe are not compilant with \u0027external world\u0027\n\nIn the end it may be not that easy to implement robust and secure solution.","commit_id":"cb7fc464e24f52bdc3a4714cadb4a9a3909005b9"},{"author":{"_account_id":6534,"name":"David Chadwick","email":"d.w.chadwick@truetrust.co.uk","username":"d-w-chadwick"},"change_message_id":"cf37302d0407166b9b99250427f4a6aa1aa04f5a","unresolved":false,"context_lines":[{"line_number":227,"context_line":"        At which point a mapping associated with the protocol and IdP can"},{"line_number":228,"context_line":"        be executed via the mapping engine. The user will also have to"},{"line_number":229,"context_line":"        include a token from ACME so as to prove they are coming from a"},{"line_number":230,"context_line":"        trusted IdP."},{"line_number":231,"context_line":""},{"line_number":232,"context_line":"   (D)  Once the token is verified by checking the signature, a service"},{"line_number":233,"context_line":"        catalog can be returned that contains BETA\u0027s services."}],"source_content_type":"text/x-rst","patch_set":11,"id":"1ae5cdf2_6e8336cb","line":230,"in_reply_to":"1ae5cdf2_901c2b15","updated":"2014-06-26 21:05:27.000000000","message":"I would like to address this point that Marek made\n\n\"If we want to use existing protocols like SAML/oidc and align with its original design there will be no assertion present at the point of sending HTTP request to http://BETA.IP.COM/v3/OS-FEDERATION/identity_provider/ACME/protocol/ext-keystone/auth. This means there is no way to do the mapping. \"\n\nThe only conclusion I can draw from the above is the original federated Keystone design has not quite got it correct yet. My reasons are as follows:\n\n1. The client always has to have a token otherwise Keystone cannot authorise the user.\n\n2. It does not matter what format the token is in, whether it is a SAML assertion, a Keystone token, or an OpenID credential. The token should be opaque to the client, and only the recipient (Keystone) should know how to process it.\n\n3. Since the user must always have a token, then it should always be possible to do attribute mappings (otherwise the token is not fit for purpose).\n\nIn the revised mapping spec that Kristy and I are writing, we have solved the attribute mapping issue by requiring each protocol handling module to always return the same (protocol independent) information to Keystone. The protocol handling module takes the token in the format (only) it can handle, and extracts the necessary information from it. So we need a module to handle SAML assertions, Apache http headers, ABFAB messages, Keystone tokens, OpenID messages etc, and all of them return exactly the same JSON data structure to Keystone ready for it to do the attribute mapping. It works, we implemented it last year and have working code and demos.","commit_id":"cb7fc464e24f52bdc3a4714cadb4a9a3909005b9"},{"author":{"_account_id":6534,"name":"David Chadwick","email":"d.w.chadwick@truetrust.co.uk","username":"d-w-chadwick"},"change_message_id":"f47ab269a8b0490003b4956ec1eba5db2a283899","unresolved":false,"context_lines":[{"line_number":228,"context_line":"        be executed via the mapping engine. The user will also have to"},{"line_number":229,"context_line":"        include a token from ACME so as to prove they are coming from a"},{"line_number":230,"context_line":"        trusted IdP."},{"line_number":231,"context_line":""},{"line_number":232,"context_line":"   (D)  Once the token is verified by checking the signature, a service"},{"line_number":233,"context_line":"        catalog can be returned that contains BETA\u0027s services."},{"line_number":234,"context_line":""}],"source_content_type":"text/x-rst","patch_set":11,"id":"1ae5cdf2_d0abfc85","line":231,"updated":"2014-06-27 05:16:22.000000000","message":"One can see that by adding IdP 1 into the mix, that the user initially gets a SAML token from IdP1, swaps it into an ACME token issued by ACME\u0027s Keystone, then presents this to BETA. However, the Keystone token needs enhancing to show its provenance, ie. that the user originally authenticated at IdP1 and not ACME, so that BETA can decide if it trusts IDP1 to be an IDP or not. So we need a trust rule to say that ACME is a trusted proxy IDP. ie. the following trust rules need adding\n\n\nBETA is configured that IDP1 is a trusted IDP\n\nBETA is configured that ACME is a trusted proxy IDP\n\n\n(Note ACME can be both a trusted proxy IdP and a trusted IDP)","commit_id":"cb7fc464e24f52bdc3a4714cadb4a9a3909005b9"},{"author":{"_account_id":6482,"name":"Steve Martinelli","email":"s.martinelli@gmail.com","username":"stevemar"},"change_message_id":"9bca58cd0352343d76356b106af8ac1e281344bc","unresolved":false,"context_lines":[{"line_number":228,"context_line":"        be executed via the mapping engine. The user will also have to"},{"line_number":229,"context_line":"        include a token from ACME so as to prove they are coming from a"},{"line_number":230,"context_line":"        trusted IdP."},{"line_number":231,"context_line":""},{"line_number":232,"context_line":"   (D)  Once the token is verified by checking the signature, a service"},{"line_number":233,"context_line":"        catalog can be returned that contains BETA\u0027s services."},{"line_number":234,"context_line":""}],"source_content_type":"text/x-rst","patch_set":11,"id":"1ae5cdf2_3bfec1af","line":231,"in_reply_to":"1ae5cdf2_d0abfc85","updated":"2014-06-27 05:54:54.000000000","message":"morgan, marek and I talked about enhancing the token before your comments were made, but I hadn\u0027t posted a new version yet. check out line 380 in the new patch set.","commit_id":"cb7fc464e24f52bdc3a4714cadb4a9a3909005b9"},{"author":{"_account_id":6482,"name":"Steve Martinelli","email":"s.martinelli@gmail.com","username":"stevemar"},"change_message_id":"78e64bea9788e1ac436f5be59e1227c1987d8c8c","unresolved":false,"context_lines":[{"line_number":231,"context_line":""},{"line_number":232,"context_line":"   (D)  Once the token is verified by checking the signature, a service"},{"line_number":233,"context_line":"        catalog can be returned that contains BETA\u0027s services."},{"line_number":234,"context_line":""},{"line_number":235,"context_line":"Alternatives"},{"line_number":236,"context_line":"------------"},{"line_number":237,"context_line":""}],"source_content_type":"text/x-rst","patch_set":11,"id":"1ae5cdf2_300b57d6","line":234,"updated":"2014-06-26 15:08:32.000000000","message":"Chadwick\u0027s original comment:\n\nNote. We need to add another diagram showing the case where a proxy IdP GAMMA is involved in the exchange","commit_id":"cb7fc464e24f52bdc3a4714cadb4a9a3909005b9"},{"author":{"_account_id":8978,"name":"Marek Denis","email":"marek.denis+openstack@gmail.com","username":"marek-denis"},"change_message_id":"7aa1bca8ec97e45c767f0152860a8f9aa258b6a9","unresolved":false,"context_lines":[{"line_number":260,"context_line":"   (G)  BETA validates the token, sees it was issued by ACME who is trusted,"},{"line_number":261,"context_line":"        and maps ACME\u0027s project or domain into a project or domain at BETA."},{"line_number":262,"context_line":"        BETA returns a valid token scoped to mapped project or domain."},{"line_number":263,"context_line":""},{"line_number":264,"context_line":"Alternatives"},{"line_number":265,"context_line":"------------"},{"line_number":266,"context_line":""}],"source_content_type":"text/x-rst","patch_set":12,"id":"1ae5cdf2_8335abf8","line":263,"updated":"2014-06-27 11:25:30.000000000","message":"excellent!","commit_id":"1b8ef85b0caaf3e69acbc909bff67f4f3312400d"},{"author":{"_account_id":8978,"name":"Marek Denis","email":"marek.denis+openstack@gmail.com","username":"marek-denis"},"change_message_id":"7aa1bca8ec97e45c767f0152860a8f9aa258b6a9","unresolved":false,"context_lines":[{"line_number":389,"context_line":"Other End User Impact"},{"line_number":390,"context_line":"---------------------"},{"line_number":391,"context_line":""},{"line_number":392,"context_line":"Potentially via ECP (https://wiki.shibboleth.net/confluence/display/SHIB2/ECP)"},{"line_number":393,"context_line":""},{"line_number":394,"context_line":"Performance Impact"},{"line_number":395,"context_line":"------------------"}],"source_content_type":"text/x-rst","patch_set":12,"id":"1ae5cdf2_5e7376b3","line":392,"updated":"2014-06-27 11:25:30.000000000","message":"looks like we are no longer using SAML w/ ECP","commit_id":"1b8ef85b0caaf3e69acbc909bff67f4f3312400d"},{"author":{"_account_id":11022,"name":"Rodrigo Duarte Sousa","email":"rodrigodsousa@gmail.com","username":"rodrigods"},"change_message_id":"6e35752ae03b7d36094d4a762567ef1fbd403161","unresolved":false,"context_lines":[{"line_number":76,"context_line":""},{"line_number":77,"context_line":"1. The solution needs to be recursive, so that if Cloud A burst to Cloud B"},{"line_number":78,"context_line":"when it is overloaded, and Cloud B burst to Cloud C when it is overloaded,"},{"line_number":79,"context_line":"then jobs from A can be burst to C via B."},{"line_number":80,"context_line":""},{"line_number":81,"context_line":"2. The solution needs to require minimum changes to existing non-Keystone"},{"line_number":82,"context_line":"components, i.e., both clients and OpenStack services, or to put it another"}],"source_content_type":"text/x-rst","patch_set":13,"id":"1ae5cdf2_37440872","line":79,"updated":"2014-06-27 13:48:09.000000000","message":"I think that a user case illustrating this requirement is necessary.\n\nOne can be an extension from Use Case 1:\nThe public service provider, used by CERN, could have some overload or outages problems. If there is some QoS agreements, between CERN and the service provider, it would need to burst to another service provider in a geographically near region.\n\nMakes sense?","commit_id":"8e458de7d5cee367e3efef61299dffde5bea5add"},{"author":{"_account_id":5956,"name":"Kristy Siu","email":"kwss@kent.ac.uk","username":"kwss"},"change_message_id":"a043bfdd9c8ca470e0417e361ffd55b987bba5e0","unresolved":false,"context_lines":[{"line_number":337,"context_line":"        \"identity_provider\": {"},{"line_number":338,"context_line":"            \"description\": \"ACME\u0027s identity provider\","},{"line_number":339,"context_line":"            \"enabled\": true,"},{"line_number":340,"context_line":"            \"id\": \"ACEM_IdP\","},{"line_number":341,"context_line":"            \"signing_key\": \"signing_key_value\""},{"line_number":342,"context_line":"        }"},{"line_number":343,"context_line":"    }"}],"source_content_type":"text/x-rst","patch_set":13,"id":"1ae5cdf2_f2638e3e","line":340,"updated":"2014-06-27 14:11:34.000000000","message":"ACME*","commit_id":"8e458de7d5cee367e3efef61299dffde5bea5add"},{"author":{"_account_id":5707,"name":"Henry Nash","email":"henryn@linux.vnet.ibm.com","username":"henry-nash"},"change_message_id":"e45f7053a833135abf36c6423cfac1cdcfdd39ab","unresolved":false,"context_lines":[{"line_number":252,"context_line":"   (D)  User scopes to a project or domain at ACME, and requests that the BETA"},{"line_number":253,"context_line":"        SP is used."},{"line_number":254,"context_line":""},{"line_number":255,"context_line":"   (E)  ACME returns a token, scoped to the requested project or domain, and"},{"line_number":256,"context_line":"        makes it usable with BETA only."},{"line_number":257,"context_line":""},{"line_number":258,"context_line":"   (F)  User authenticates with BETA, presenting the token returned from (D)"}],"source_content_type":"text/x-rst","patch_set":14,"id":"dab895d6_4e4fef92","line":255,"updated":"2014-06-29 16:08:05.000000000","message":"How does ACME know that the user has a role on the request project/domain (assuming this project/domain is actually owned by BETA)? Or is this my major mis-understanding of this whole idea...that ACME has the \"master\" authorization info for any SP that it is going to use?  If so, what is held in BETA exactly?\n\nIt\u0027s unclear what the advantage of actually getting the scoped token from ACME is?  Why wouldn\u0027t the user just make a federated auth request to BETA having found out where to send it from the extended catalog it got from ACME?  Is it that we don\u0027t want to expose the IdP trust that ACME has to BETA and we using the k2k token to provide that opaqueness?","commit_id":"2afc819898b3a28a7a5f7c584aa1161b175460bb"},{"author":{"_account_id":6482,"name":"Steve Martinelli","email":"s.martinelli@gmail.com","username":"stevemar"},"change_message_id":"6ede403087f863349d3275b4e8d27e90f9d44d35","unresolved":false,"context_lines":[{"line_number":252,"context_line":"   (D)  User scopes to a project or domain at ACME, and requests that the BETA"},{"line_number":253,"context_line":"        SP is used."},{"line_number":254,"context_line":""},{"line_number":255,"context_line":"   (E)  ACME returns a token, scoped to the requested project or domain, and"},{"line_number":256,"context_line":"        makes it usable with BETA only."},{"line_number":257,"context_line":""},{"line_number":258,"context_line":"   (F)  User authenticates with BETA, presenting the token returned from (D)"}],"source_content_type":"text/x-rst","patch_set":14,"id":"dab895d6_583174a1","line":255,"in_reply_to":"dab895d6_4e4fef92","updated":"2014-06-29 21:04:21.000000000","message":"It\u0027s unclear what the advantage of actually getting the scoped token from ACME is?\n\n  We want the scoped token from ACME because the user \n  has authorization on that project or domain.\n  We can send the scoped token as basically assertion data\n  to BETA.\n  BETA and ACME should have agreed that project X or\n  domain Y on ACME has the same access as project P or\n  domain D on BETA.\n  We can use the mapping engine to crunch through the\n  scoped token\u0027s (assertion), and the defined mapping.\n\nWhy wouldn\u0027t the user just make a federated auth request to BETA having found out where to send it from the extended catalog it got from ACME?\n\n  Because then the user would have to know about BETA\u0027s\n  project or domain ids beforehand.","commit_id":"2afc819898b3a28a7a5f7c584aa1161b175460bb"},{"author":{"_account_id":5707,"name":"Henry Nash","email":"henryn@linux.vnet.ibm.com","username":"henry-nash"},"change_message_id":"eb1d1bfbf9d7d96c53625618c3677bdd9fe98108","unresolved":false,"context_lines":[{"line_number":252,"context_line":"   (D)  User scopes to a project or domain at ACME, and requests that the BETA"},{"line_number":253,"context_line":"        SP is used."},{"line_number":254,"context_line":""},{"line_number":255,"context_line":"   (E)  ACME returns a token, scoped to the requested project or domain, and"},{"line_number":256,"context_line":"        makes it usable with BETA only."},{"line_number":257,"context_line":""},{"line_number":258,"context_line":"   (F)  User authenticates with BETA, presenting the token returned from (D)"}],"source_content_type":"text/x-rst","patch_set":14,"id":"dab895d6_58f33473","line":255,"in_reply_to":"dab895d6_583174a1","updated":"2014-06-29 23:03:41.000000000","message":"So to make this work, somehow out of band the roles on, say, the project in question need to be (effectively) replicated between ACME and BETA?  That sounds weird (and fraught with problems).\n\nWouldn\u0027t it just be that ACME defines which roles the users has on Project X?  These roles then essentially become attributes of the keystone assertion token that the user receives from ACME and sends to BETA.  Then it is entirely up to BETA what it maps these \"assertion role/attributes\" to.  Could be to Project P (but the role names could be totally different), or could be to a role in a group that gets them access to all projects in BETA, etc.  If the above is what we really mean, then what we are really saying is that a Keystone IdP\u0027s (i.e.  ACME) attribute currency are keystone role assignments.  For K2K federation, that\u0027s the input into the mapper of any SP using that keystone IdP.  Is this what we mean?","commit_id":"2afc819898b3a28a7a5f7c584aa1161b175460bb"},{"author":{"_account_id":6482,"name":"Steve Martinelli","email":"s.martinelli@gmail.com","username":"stevemar"},"change_message_id":"dcdccd5577b4aabb891a9258d9ca50cfa511cf22","unresolved":false,"context_lines":[{"line_number":252,"context_line":"   (D)  User scopes to a project or domain at ACME, and requests that the BETA"},{"line_number":253,"context_line":"        SP is used."},{"line_number":254,"context_line":""},{"line_number":255,"context_line":"   (E)  ACME returns a token, scoped to the requested project or domain, and"},{"line_number":256,"context_line":"        makes it usable with BETA only."},{"line_number":257,"context_line":""},{"line_number":258,"context_line":"   (F)  User authenticates with BETA, presenting the token returned from (D)"}],"source_content_type":"text/x-rst","patch_set":14,"id":"dab895d6_ccd062fa","line":255,"in_reply_to":"dab895d6_58f33473","updated":"2014-06-30 05:06:10.000000000","message":"Refer to my answer for Kristy\u0027s question, (and also her question).\n\nI\u0027m not hard set on any one approach, I just want my credentials to work on another Keystone. This is what was discussed on Friday between a few of us on IRC and seemed to make sense at the time.","commit_id":"2afc819898b3a28a7a5f7c584aa1161b175460bb"},{"author":{"_account_id":5707,"name":"Henry Nash","email":"henryn@linux.vnet.ibm.com","username":"henry-nash"},"change_message_id":"110fa13d082fb5244b6cf6cca78d90e1c1764071","unresolved":false,"context_lines":[{"line_number":252,"context_line":"   (D)  User scopes to a project or domain at ACME, and requests that the BETA"},{"line_number":253,"context_line":"        SP is used."},{"line_number":254,"context_line":""},{"line_number":255,"context_line":"   (E)  ACME returns a token, scoped to the requested project or domain, and"},{"line_number":256,"context_line":"        makes it usable with BETA only."},{"line_number":257,"context_line":""},{"line_number":258,"context_line":"   (F)  User authenticates with BETA, presenting the token returned from (D)"}],"source_content_type":"text/x-rst","patch_set":14,"id":"dab895d6_01e4dc0b","line":255,"in_reply_to":"dab895d6_ccd062fa","updated":"2014-06-30 10:05:57.000000000","message":"ah, right...yes, just saw that...looks like we are kind of saying the same thing...","commit_id":"2afc819898b3a28a7a5f7c584aa1161b175460bb"},{"author":{"_account_id":5707,"name":"Henry Nash","email":"henryn@linux.vnet.ibm.com","username":"henry-nash"},"change_message_id":"e45f7053a833135abf36c6423cfac1cdcfdd39ab","unresolved":false,"context_lines":[{"line_number":259,"context_line":""},{"line_number":260,"context_line":"   (G)  BETA validates the token, sees it was issued by ACME who is trusted,"},{"line_number":261,"context_line":"        and maps ACME\u0027s project or domain into a project or domain at BETA."},{"line_number":262,"context_line":"        BETA returns a valid token scoped to mapped project or domain."},{"line_number":263,"context_line":""},{"line_number":264,"context_line":"Alternatives"},{"line_number":265,"context_line":"------------"}],"source_content_type":"text/x-rst","patch_set":14,"id":"dab895d6_ee052315","line":262,"updated":"2014-06-29 16:08:05.000000000","message":"Is the idea that we use the existing federated mapper for this?  If so, it would be worth saying that.  Are any extensions to it needed?","commit_id":"2afc819898b3a28a7a5f7c584aa1161b175460bb"},{"author":{"_account_id":6482,"name":"Steve Martinelli","email":"s.martinelli@gmail.com","username":"stevemar"},"change_message_id":"95a43ee599b0cbd0369baafbb42b28f5865f6694","unresolved":false,"context_lines":[{"line_number":259,"context_line":""},{"line_number":260,"context_line":"   (G)  BETA validates the token, sees it was issued by ACME who is trusted,"},{"line_number":261,"context_line":"        and maps ACME\u0027s project or domain into a project or domain at BETA."},{"line_number":262,"context_line":"        BETA returns a valid token scoped to mapped project or domain."},{"line_number":263,"context_line":""},{"line_number":264,"context_line":"Alternatives"},{"line_number":265,"context_line":"------------"}],"source_content_type":"text/x-rst","patch_set":14,"id":"baada198_27882422","line":262,"in_reply_to":"dab895d6_494ef6c2","updated":"2014-06-30 16:26:38.000000000","message":"Yeah, I don\u0027t see an issue in why we can\u0027t do both, the mapping engine should be flexible enough to handle a mapping for an unscoped token (projects to groups), or a scoped token (projects to projects). \n\nEither way, the logic necessary to the second step should be independent of getting this spec complete.","commit_id":"2afc819898b3a28a7a5f7c584aa1161b175460bb"},{"author":{"_account_id":6482,"name":"Steve Martinelli","email":"s.martinelli@gmail.com","username":"stevemar"},"change_message_id":"dcdccd5577b4aabb891a9258d9ca50cfa511cf22","unresolved":false,"context_lines":[{"line_number":259,"context_line":""},{"line_number":260,"context_line":"   (G)  BETA validates the token, sees it was issued by ACME who is trusted,"},{"line_number":261,"context_line":"        and maps ACME\u0027s project or domain into a project or domain at BETA."},{"line_number":262,"context_line":"        BETA returns a valid token scoped to mapped project or domain."},{"line_number":263,"context_line":""},{"line_number":264,"context_line":"Alternatives"},{"line_number":265,"context_line":"------------"}],"source_content_type":"text/x-rst","patch_set":14,"id":"dab895d6_8cfe6a6a","line":262,"in_reply_to":"dab895d6_58a6d4c2","updated":"2014-06-30 05:06:10.000000000","message":"I think we are in agreement that a scoped token would need to be present??\n\nAnd yes, that approach could definitely work, though the end user would then have to re-scope the token.\n\nI think we can make any mapping enhancements separately, what you suggested should work. \n\nLet me know what you think and I can draft a new version of the spec (updating step G)","commit_id":"2afc819898b3a28a7a5f7c584aa1161b175460bb"},{"author":{"_account_id":5956,"name":"Kristy Siu","email":"kwss@kent.ac.uk","username":"kwss"},"change_message_id":"1b8ee586de952199fdd98ddceb20f2b5a53c8ca0","unresolved":false,"context_lines":[{"line_number":259,"context_line":""},{"line_number":260,"context_line":"   (G)  BETA validates the token, sees it was issued by ACME who is trusted,"},{"line_number":261,"context_line":"        and maps ACME\u0027s project or domain into a project or domain at BETA."},{"line_number":262,"context_line":"        BETA returns a valid token scoped to mapped project or domain."},{"line_number":263,"context_line":""},{"line_number":264,"context_line":"Alternatives"},{"line_number":265,"context_line":"------------"}],"source_content_type":"text/x-rst","patch_set":14,"id":"dab895d6_58a6d4c2","line":262,"in_reply_to":"dab895d6_7826386a","updated":"2014-06-29 21:45:51.000000000","message":"What changes would be needed to the mapping engine?\n\nCould we not just have the module which handles external token validation return the ACME roles/projects the same way as a set of SAML2 attributes?\n\nThe ACME token is scoped to project X and the mapping rule says:\n\nproject X maps to group A\n\nthen group A has a grant for project P on BETA.","commit_id":"2afc819898b3a28a7a5f7c584aa1161b175460bb"},{"author":{"_account_id":5707,"name":"Henry Nash","email":"henryn@linux.vnet.ibm.com","username":"henry-nash"},"change_message_id":"110fa13d082fb5244b6cf6cca78d90e1c1764071","unresolved":false,"context_lines":[{"line_number":259,"context_line":""},{"line_number":260,"context_line":"   (G)  BETA validates the token, sees it was issued by ACME who is trusted,"},{"line_number":261,"context_line":"        and maps ACME\u0027s project or domain into a project or domain at BETA."},{"line_number":262,"context_line":"        BETA returns a valid token scoped to mapped project or domain."},{"line_number":263,"context_line":""},{"line_number":264,"context_line":"Alternatives"},{"line_number":265,"context_line":"------------"}],"source_content_type":"text/x-rst","patch_set":14,"id":"dab895d6_c13ae435","line":262,"in_reply_to":"dab895d6_8cfe6a6a","updated":"2014-06-30 10:05:57.000000000","message":"I agree with this idea....this was the light bulb moment for me when I thought about the idea that the role assignments in the token from ACME were in fact the \"Keystone assertion attributes\" that are used by BETA to do a mapping.  I think that this would be a useful way of describing this, e.g.:\n\n(E)  ACME returns a token, scoped to the requested project or domain, and makes it usable with BETA only.  The role assignments in this token represent the Keystone assertion attributes that a user can then pass to BETA.\n\n(F)  User authenticates with BETA, presenting the token returned from (D)\t\n\n(G)  BETA validates the token, sees it was issued by ACME who is trusted.  The role assignments in this token are treated as assertion attributes and fed into BETAs federated mapping rules, resulting in a new set of assignments on a project or domain in BETA.  BETA  returns a valid token scoped to the mapped project or domain and the respective assignments.","commit_id":"2afc819898b3a28a7a5f7c584aa1161b175460bb"},{"author":{"_account_id":8978,"name":"Marek Denis","email":"marek.denis+openstack@gmail.com","username":"marek-denis"},"change_message_id":"e4c2e8f0b162b25010f01ae52643dc358615b6cf","unresolved":false,"context_lines":[{"line_number":259,"context_line":""},{"line_number":260,"context_line":"   (G)  BETA validates the token, sees it was issued by ACME who is trusted,"},{"line_number":261,"context_line":"        and maps ACME\u0027s project or domain into a project or domain at BETA."},{"line_number":262,"context_line":"        BETA returns a valid token scoped to mapped project or domain."},{"line_number":263,"context_line":""},{"line_number":264,"context_line":"Alternatives"},{"line_number":265,"context_line":"------------"}],"source_content_type":"text/x-rst","patch_set":14,"id":"dab895d6_494ef6c2","line":262,"in_reply_to":"dab895d6_c13ae435","updated":"2014-06-30 14:50:19.000000000","message":"I don\u0027t see anything bad with mapping projects to projects and domains to domains. \nSteve was right that mapping project -\u003e groups -\u003e roles would introduce another step - scoping the BETA token. \nHowever, I think we should not limit mapping to X-\u003e X\u0027 (projects or domains) only, but  make sure mapping remains flexible enough to  configure per-user/group access to remote project/domain.","commit_id":"2afc819898b3a28a7a5f7c584aa1161b175460bb"},{"author":{"_account_id":6482,"name":"Steve Martinelli","email":"s.martinelli@gmail.com","username":"stevemar"},"change_message_id":"95a43ee599b0cbd0369baafbb42b28f5865f6694","unresolved":false,"context_lines":[{"line_number":259,"context_line":""},{"line_number":260,"context_line":"   (G)  BETA validates the token, sees it was issued by ACME who is trusted,"},{"line_number":261,"context_line":"        and maps ACME\u0027s project or domain into a project or domain at BETA."},{"line_number":262,"context_line":"        BETA returns a valid token scoped to mapped project or domain."},{"line_number":263,"context_line":""},{"line_number":264,"context_line":"Alternatives"},{"line_number":265,"context_line":"------------"}],"source_content_type":"text/x-rst","patch_set":14,"id":"baada198_c7e3e803","line":262,"in_reply_to":"dab895d6_c13ae435","updated":"2014-06-30 16:26:38.000000000","message":"hooray for light bulb moments! \n\nyep, token data is just a keystone assertion IMO.\n\nyour steps look good to me, i\u0027ll update the spec with that.","commit_id":"2afc819898b3a28a7a5f7c584aa1161b175460bb"},{"author":{"_account_id":6482,"name":"Steve Martinelli","email":"s.martinelli@gmail.com","username":"stevemar"},"change_message_id":"6ede403087f863349d3275b4e8d27e90f9d44d35","unresolved":false,"context_lines":[{"line_number":259,"context_line":""},{"line_number":260,"context_line":"   (G)  BETA validates the token, sees it was issued by ACME who is trusted,"},{"line_number":261,"context_line":"        and maps ACME\u0027s project or domain into a project or domain at BETA."},{"line_number":262,"context_line":"        BETA returns a valid token scoped to mapped project or domain."},{"line_number":263,"context_line":""},{"line_number":264,"context_line":"Alternatives"},{"line_number":265,"context_line":"------------"}],"source_content_type":"text/x-rst","patch_set":14,"id":"dab895d6_7826386a","line":262,"in_reply_to":"dab895d6_ee052315","updated":"2014-06-29 21:04:21.000000000","message":"yep! I\u0027ll make a note of mentioning that then.\n\nand yes, we would have to enhance the mapping engine","commit_id":"2afc819898b3a28a7a5f7c584aa1161b175460bb"},{"author":{"_account_id":6534,"name":"David Chadwick","email":"d.w.chadwick@truetrust.co.uk","username":"d-w-chadwick"},"change_message_id":"8e9bf0993de9dd656065dfed32514fd995194e72","unresolved":false,"context_lines":[{"line_number":31,"context_line":""},{"line_number":32,"context_line":"* End user - An identity with access to one or many OpenStack clouds."},{"line_number":33,"context_line":""},{"line_number":34,"context_line":"In the Icehouse release, we identified a way to establish trust between an"},{"line_number":35,"context_line":"IdP and Keystone. This allowed Cloud Implementers to set-up single-sign-on"},{"line_number":36,"context_line":"when configuring their cloud and not incur the administrative overhead"},{"line_number":37,"context_line":"that comes with provisioning identities in Keystone. Keystone trusts the"}],"source_content_type":"text/x-rst","patch_set":15,"id":"baada198_750602d0","line":34,"updated":"2014-07-02 06:17:49.000000000","message":"a SAML","commit_id":"f25492250f1f6553560255c6b947166f9ddd7d41"},{"author":{"_account_id":4,"name":"Dolph Mathews","email":"dolph.mathews@gmail.com","username":"dolph"},"change_message_id":"f64dda59246ad75536f26861ba52f7a16651cc03","unresolved":false,"context_lines":[{"line_number":31,"context_line":""},{"line_number":32,"context_line":"* End user - An identity with access to one or many OpenStack clouds."},{"line_number":33,"context_line":""},{"line_number":34,"context_line":"In the Icehouse release, we identified a way to establish trust between an"},{"line_number":35,"context_line":"IdP and Keystone. This allowed Cloud Implementers to set-up single-sign-on"},{"line_number":36,"context_line":"when configuring their cloud and not incur the administrative overhead"},{"line_number":37,"context_line":"that comes with provisioning identities in Keystone. Keystone trusts the"}],"source_content_type":"text/x-rst","patch_set":15,"id":"baada198_edd6b8c2","line":34,"in_reply_to":"baada198_750602d0","updated":"2014-07-02 15:03:25.000000000","message":"Done","commit_id":"f25492250f1f6553560255c6b947166f9ddd7d41"},{"author":{"_account_id":1228,"name":"Joe Savak","email":"jsavak@gmail.com","username":"jsavak"},"change_message_id":"9c222f644619dab476c212ed334e9d1ffd9cc701","unresolved":false,"context_lines":[{"line_number":77,"context_line":"1. The solution needs to be recursive, so that if Cloud A burst to Cloud B"},{"line_number":78,"context_line":"when it is overloaded, and Cloud B burst to Cloud C when it is overloaded,"},{"line_number":79,"context_line":"then jobs from A can be burst to C via B."},{"line_number":80,"context_line":""},{"line_number":81,"context_line":"2. The solution needs to require minimum changes to existing non-Keystone"},{"line_number":82,"context_line":"components, i.e., both clients and OpenStack services, or to put it another"},{"line_number":83,"context_line":"way, the majority of the changes should be applied to Keystone."}],"source_content_type":"text/x-rst","patch_set":15,"id":"baada198_77542354","line":80,"updated":"2014-07-10 19:58:42.000000000","message":"Current discussion is that this doesn\u0027t need to be a recursive trust necessarily. Having transitive trust as illustrated in this requirement adds quite a bit of security concerns (A doesn\u0027t necessarily trust C and C could be a corrupted cloud or bad-actor).","commit_id":"f25492250f1f6553560255c6b947166f9ddd7d41"},{"author":{"_account_id":1228,"name":"Joe Savak","email":"jsavak@gmail.com","username":"jsavak"},"change_message_id":"9c222f644619dab476c212ed334e9d1ffd9cc701","unresolved":false,"context_lines":[{"line_number":97,"context_line":"and Openstack, i.e., we must not downgrade the overall security by the"},{"line_number":98,"context_line":"introduction of Keystone federation. On the other hand it does not need to be"},{"line_number":99,"context_line":"more secure since attackers will always go for the weakest link."},{"line_number":100,"context_line":""},{"line_number":101,"context_line":"5. The solution must not reduce the functionality of existing clients and"},{"line_number":102,"context_line":"services."},{"line_number":103,"context_line":""}],"source_content_type":"text/x-rst","patch_set":15,"id":"baada198_978457b2","line":100,"updated":"2014-07-10 19:58:42.000000000","message":"The solution can offer various degrees of security, based on the trust needed by the implementer. For example, it could be a fully trusted recently acquired cloud which doesn\u0027t need 2nd-factor authentication such as x509/token-binding. Or it could be a semi-trusted cloud where some customer experience can be sacrificed for tighter security.","commit_id":"f25492250f1f6553560255c6b947166f9ddd7d41"},{"author":{"_account_id":8978,"name":"Marek Denis","email":"marek.denis+openstack@gmail.com","username":"marek-denis"},"change_message_id":"f3add3146db2b554a849f7c0c7a46b003218c3cf","unresolved":false,"context_lines":[{"line_number":144,"context_line":""},{"line_number":145,"context_line":"2. ACME\u0027s Keystone mentioned in the above use cases should have knowledge"},{"line_number":146,"context_line":"of what services and endpoints BETA offers so that it could build adequate"},{"line_number":147,"context_line":"token scope across both OpenStack clouds."},{"line_number":148,"context_line":""},{"line_number":149,"context_line":"3. BETA\u0027s Keystone, acting as a trusted service provider, will get many tokens"},{"line_number":150,"context_line":"that are not within its local store. It will need to be able to decipher"}],"source_content_type":"text/x-rst","patch_set":15,"id":"baada198_2c3600e8","line":147,"updated":"2014-07-02 10:33:44.000000000","message":"I don\u0027t remember if we have discussed it but since user@ACME still need to get token usable with BETA, and this means he needs to contact BETA\u0027s Keystone I\u0027d say BETA\u0027s full service catalog is unnecessary. User, when connecting to ACME\u0027s Keystone should be good to get remote Keystones.\n\nAnd this \u0027extended\u0027 Service Catalog could be built from active and registered Service Providers","commit_id":"f25492250f1f6553560255c6b947166f9ddd7d41"},{"author":{"_account_id":6482,"name":"Steve Martinelli","email":"s.martinelli@gmail.com","username":"stevemar"},"change_message_id":"d929fa17786153dcc30ece458d8c6356d2613c02","unresolved":false,"context_lines":[{"line_number":144,"context_line":""},{"line_number":145,"context_line":"2. ACME\u0027s Keystone mentioned in the above use cases should have knowledge"},{"line_number":146,"context_line":"of what services and endpoints BETA offers so that it could build adequate"},{"line_number":147,"context_line":"token scope across both OpenStack clouds."},{"line_number":148,"context_line":""},{"line_number":149,"context_line":"3. BETA\u0027s Keystone, acting as a trusted service provider, will get many tokens"},{"line_number":150,"context_line":"that are not within its local store. It will need to be able to decipher"}],"source_content_type":"text/x-rst","patch_set":15,"id":"baada198_d324ea0e","line":147,"in_reply_to":"baada198_0107fb82","updated":"2014-07-04 06:03:01.000000000","message":"Yeah, maybe \u0027extended\u0027 SC isn\u0027t the right term here.\nAll we really need is BETA\u0027s auth url right? or a list of all SP urls?","commit_id":"f25492250f1f6553560255c6b947166f9ddd7d41"},{"author":{"_account_id":4,"name":"Dolph Mathews","email":"dolph.mathews@gmail.com","username":"dolph"},"change_message_id":"049fb0bc89e4e741d78ec79da48641d9c311ad3d","unresolved":false,"context_lines":[{"line_number":144,"context_line":""},{"line_number":145,"context_line":"2. ACME\u0027s Keystone mentioned in the above use cases should have knowledge"},{"line_number":146,"context_line":"of what services and endpoints BETA offers so that it could build adequate"},{"line_number":147,"context_line":"token scope across both OpenStack clouds."},{"line_number":148,"context_line":""},{"line_number":149,"context_line":"3. BETA\u0027s Keystone, acting as a trusted service provider, will get many tokens"},{"line_number":150,"context_line":"that are not within its local store. It will need to be able to decipher"}],"source_content_type":"text/x-rst","patch_set":15,"id":"baada198_0107fb82","line":147,"in_reply_to":"baada198_2c3600e8","updated":"2014-07-03 20:33:34.000000000","message":"+1","commit_id":"f25492250f1f6553560255c6b947166f9ddd7d41"},{"author":{"_account_id":8978,"name":"Marek Denis","email":"marek.denis+openstack@gmail.com","username":"marek-denis"},"change_message_id":"a3aad36b855def0864216f36fd20ce81a96d43bf","unresolved":false,"context_lines":[{"line_number":144,"context_line":""},{"line_number":145,"context_line":"2. ACME\u0027s Keystone mentioned in the above use cases should have knowledge"},{"line_number":146,"context_line":"of what services and endpoints BETA offers so that it could build adequate"},{"line_number":147,"context_line":"token scope across both OpenStack clouds."},{"line_number":148,"context_line":""},{"line_number":149,"context_line":"3. BETA\u0027s Keystone, acting as a trusted service provider, will get many tokens"},{"line_number":150,"context_line":"that are not within its local store. It will need to be able to decipher"}],"source_content_type":"text/x-rst","patch_set":15,"id":"baada198_4b0ae279","line":147,"in_reply_to":"baada198_d324ea0e","updated":"2014-07-04 07:37:10.000000000","message":"Steve: In the current design - yes. Probably wrapped with well known structures like \u0027endpoint\u0027 or things like that. We should also consider multiple endpoints if for instance remoute cloud has multiple Keystones available.","commit_id":"f25492250f1f6553560255c6b947166f9ddd7d41"},{"author":{"_account_id":6534,"name":"David Chadwick","email":"d.w.chadwick@truetrust.co.uk","username":"d-w-chadwick"},"change_message_id":"8e9bf0993de9dd656065dfed32514fd995194e72","unresolved":false,"context_lines":[{"line_number":145,"context_line":"2. ACME\u0027s Keystone mentioned in the above use cases should have knowledge"},{"line_number":146,"context_line":"of what services and endpoints BETA offers so that it could build adequate"},{"line_number":147,"context_line":"token scope across both OpenStack clouds."},{"line_number":148,"context_line":""},{"line_number":149,"context_line":"3. BETA\u0027s Keystone, acting as a trusted service provider, will get many tokens"},{"line_number":150,"context_line":"that are not within its local store. It will need to be able to decipher"},{"line_number":151,"context_line":"where the originating Keystone is from. The token can be validated if it is"}],"source_content_type":"text/x-rst","patch_set":15,"id":"baada198_958c7637","line":148,"updated":"2014-07-02 06:17:49.000000000","message":"Note that if BETA is obtaining some of its services from DELTA (i.e. uses it as a service provider), then this will not be known to ACME (or initially to ACME\u0027s users), as BETA is responsible for this subcontracting/outsourcing/cloud bursting and takes full responsibility for this. However, when ACME\u0027s users contact BETA to obtain a service, then BETA will inform the users about DELTA| if they ask for an extended service catalog.","commit_id":"f25492250f1f6553560255c6b947166f9ddd7d41"},{"author":{"_account_id":4,"name":"Dolph Mathews","email":"dolph.mathews@gmail.com","username":"dolph"},"change_message_id":"049fb0bc89e4e741d78ec79da48641d9c311ad3d","unresolved":false,"context_lines":[{"line_number":145,"context_line":"2. ACME\u0027s Keystone mentioned in the above use cases should have knowledge"},{"line_number":146,"context_line":"of what services and endpoints BETA offers so that it could build adequate"},{"line_number":147,"context_line":"token scope across both OpenStack clouds."},{"line_number":148,"context_line":""},{"line_number":149,"context_line":"3. BETA\u0027s Keystone, acting as a trusted service provider, will get many tokens"},{"line_number":150,"context_line":"that are not within its local store. It will need to be able to decipher"},{"line_number":151,"context_line":"where the originating Keystone is from. The token can be validated if it is"}],"source_content_type":"text/x-rst","patch_set":15,"id":"baada198_81d30b03","line":148,"in_reply_to":"baada198_958c7637","updated":"2014-07-03 20:33:34.000000000","message":"+1","commit_id":"f25492250f1f6553560255c6b947166f9ddd7d41"},{"author":{"_account_id":5707,"name":"Henry Nash","email":"henryn@linux.vnet.ibm.com","username":"henry-nash"},"change_message_id":"ee1925b41c6c94cf373b110b2ad039509320f749","unresolved":false,"context_lines":[{"line_number":242,"context_line":"   The flow illustrated in Figure 2 includes the following steps:"},{"line_number":243,"context_line":""},{"line_number":244,"context_line":"   (A)  User authenticates through their local IdP, and the IdP sends"},{"line_number":245,"context_line":"        assertion data to ACME."},{"line_number":246,"context_line":""},{"line_number":247,"context_line":"   (B)  User asks for an extended service catalog, possible using a query"},{"line_number":248,"context_line":"        parameter to select an SP."}],"source_content_type":"text/x-rst","patch_set":15,"id":"baada198_12687286","line":245,"updated":"2014-07-02 10:03:18.000000000","message":"As an aside, when showing this spec to others, some have been confused by this local IdP.  Essentially it is somewhat tangental to what is being proposed - i.e. although it\u0027s a good representation of what is likely to happen in practice, the k2k flow would work just fine if there was no independent IdP and the user authenticated with username and password to ACME, no?","commit_id":"f25492250f1f6553560255c6b947166f9ddd7d41"},{"author":{"_account_id":6534,"name":"David Chadwick","email":"d.w.chadwick@truetrust.co.uk","username":"d-w-chadwick"},"change_message_id":"e8080e7c86db6484519f8091c03c5f59d03db3f1","unresolved":false,"context_lines":[{"line_number":242,"context_line":"   The flow illustrated in Figure 2 includes the following steps:"},{"line_number":243,"context_line":""},{"line_number":244,"context_line":"   (A)  User authenticates through their local IdP, and the IdP sends"},{"line_number":245,"context_line":"        assertion data to ACME."},{"line_number":246,"context_line":""},{"line_number":247,"context_line":"   (B)  User asks for an extended service catalog, possible using a query"},{"line_number":248,"context_line":"        parameter to select an SP."}],"source_content_type":"text/x-rst","patch_set":15,"id":"baada198_9548ec88","line":245,"in_reply_to":"baada198_12687286","updated":"2014-07-02 11:11:36.000000000","message":"Correct. But putting in the IdP shows the recursive nature of what is being proposed and the fact that the user is exchanging a token from one IdP to a different token from a different IdP (ACME in this example)","commit_id":"f25492250f1f6553560255c6b947166f9ddd7d41"},{"author":{"_account_id":8978,"name":"Marek Denis","email":"marek.denis+openstack@gmail.com","username":"marek-denis"},"change_message_id":"3d3924254c1e47b97023c7f4c3443f71f91f4988","unresolved":false,"context_lines":[{"line_number":242,"context_line":"   The flow illustrated in Figure 2 includes the following steps:"},{"line_number":243,"context_line":""},{"line_number":244,"context_line":"   (A)  User authenticates through their local IdP, and the IdP sends"},{"line_number":245,"context_line":"        assertion data to ACME."},{"line_number":246,"context_line":""},{"line_number":247,"context_line":"   (B)  User asks for an extended service catalog, possible using a query"},{"line_number":248,"context_line":"        parameter to select an SP."}],"source_content_type":"text/x-rst","patch_set":15,"id":"baada198_b54b302a","line":245,"in_reply_to":"baada198_12687286","updated":"2014-07-02 11:22:23.000000000","message":"henry-nash: indeed this can be slightly confusing.","commit_id":"f25492250f1f6553560255c6b947166f9ddd7d41"},{"author":{"_account_id":11022,"name":"Rodrigo Duarte Sousa","email":"rodrigodsousa@gmail.com","username":"rodrigods"},"change_message_id":"6d7587805c75a9ca3bcde47bed4be00c9cfd02f7","unresolved":false,"context_lines":[{"line_number":245,"context_line":"        assertion data to ACME."},{"line_number":246,"context_line":""},{"line_number":247,"context_line":"   (B)  User asks for an extended service catalog, possible using a query"},{"line_number":248,"context_line":"        parameter to select an SP."},{"line_number":249,"context_line":""},{"line_number":250,"context_line":"   (C)  ACME returns a token with one or more SPs, BETA included."},{"line_number":251,"context_line":""}],"source_content_type":"text/x-rst","patch_set":15,"id":"baada198_6d51c80d","line":248,"updated":"2014-07-02 14:49:06.000000000","message":"This means the user had previously done a GET /OS-FEDERATION/service_providers ?\n\nAnother question is \"when ACME gets BETA\u0027s service catalog?\"","commit_id":"f25492250f1f6553560255c6b947166f9ddd7d41"},{"author":{"_account_id":9959,"name":"Craig A. Lee","email":"lee@aero.org","username":"craigalee"},"change_message_id":"9179c9965ce9f7b9eccf8c184135c0df4e0d46e1","unresolved":false,"context_lines":[{"line_number":245,"context_line":"        assertion data to ACME."},{"line_number":246,"context_line":""},{"line_number":247,"context_line":"   (B)  User asks for an extended service catalog, possible using a query"},{"line_number":248,"context_line":"        parameter to select an SP."},{"line_number":249,"context_line":""},{"line_number":250,"context_line":"   (C)  ACME returns a token with one or more SPs, BETA included."},{"line_number":251,"context_line":""}],"source_content_type":"text/x-rst","patch_set":15,"id":"baada198_911b801a","line":248,"in_reply_to":"baada198_4d640422","updated":"2014-07-03 04:57:15.000000000","message":"Actually this concerns me.   Is it the ACME Cloud Implementer that\u0027s getting the BETA SC, or is it an ACME user?  As drawn, Figure 2 says that the User gets a (possibly extended) SC from ACME, and then can make a choice about which SP to use -- ACME or BETA (or others) -- and then can get their (possibly extended) SC.  There\u0027s no real notion of automagic cloud-bursting from ACME to BETA to DELTA to whoever, where the User doesn\u0027t know where their resources are actually coming from.  I suppose the User\u0027s client could be making these decisions, but that\u0027s not transparent cloud-bursting (assuming that\u0027s what you want to do).\n\nAlso, are all ACME users authorized to know about, or use, all possible BETAs? Are all ACME customers/users authorized to cloud-burst, if they want to?  Does ACME want to offer different classes of service depending on whether you can cloud-burst or not?  Is all cloud-bursting the same?  Would ACME want to separately offer compute cloud-bursting vs. storage cloud-bursting, and manage them accordingly?\n\nI think all of this can be managed if domains are federated -- not just Keystones.  When a local user authenticates to their local Keystone with domain or project scope, the SC they get contains the BETAs they are authorized to use.  Within that domain/project, the user has a set of roles that any BETA can use to determine what services to expose to that user in the SC that gets returned from that BETA (including any DELTAs).  Of course, for each federated domain, each Keystone must have either (a) a common set of projects and roles (agreed upon out-of-band), or (b) a mapping from the ACME domain/project to an appropriate domain/project in BETA.  I\u0027m not sure how that mapping would be established or maintained.","commit_id":"f25492250f1f6553560255c6b947166f9ddd7d41"},{"author":{"_account_id":8978,"name":"Marek Denis","email":"marek.denis+openstack@gmail.com","username":"marek-denis"},"change_message_id":"d886f2a4ee8f56f9eb13fcdfe539d76713282105","unresolved":false,"context_lines":[{"line_number":245,"context_line":"        assertion data to ACME."},{"line_number":246,"context_line":""},{"line_number":247,"context_line":"   (B)  User asks for an extended service catalog, possible using a query"},{"line_number":248,"context_line":"        parameter to select an SP."},{"line_number":249,"context_line":""},{"line_number":250,"context_line":"   (C)  ACME returns a token with one or more SPs, BETA included."},{"line_number":251,"context_line":""}],"source_content_type":"text/x-rst","patch_set":15,"id":"baada198_4d640422","line":248,"in_reply_to":"baada198_6d51c80d","updated":"2014-07-02 15:06:35.000000000","message":"or, so this might need to be rephrased. The goal AFAIR was \"if you know nothing, get a full SC so you can discover who is available, if you know who you want to \n                use, don\u0027t fetch full SC, just fetch it\u0027s endpoint which saves some bandthwidth\"","commit_id":"f25492250f1f6553560255c6b947166f9ddd7d41"},{"author":{"_account_id":5707,"name":"Henry Nash","email":"henryn@linux.vnet.ibm.com","username":"henry-nash"},"change_message_id":"ee1925b41c6c94cf373b110b2ad039509320f749","unresolved":false,"context_lines":[{"line_number":250,"context_line":"   (C)  ACME returns a token with one or more SPs, BETA included."},{"line_number":251,"context_line":""},{"line_number":252,"context_line":"   (D)  User scopes to a project or domain at ACME, and requests that the"},{"line_number":253,"context_line":"        BETA SP is used."},{"line_number":254,"context_line":""},{"line_number":255,"context_line":"   (E)  ACME returns a token, scoped to the requested project or domain, and"},{"line_number":256,"context_line":"        makes it usable with BETA only. The role assignments in this token"}],"source_content_type":"text/x-rst","patch_set":15,"id":"baada198_b2afc6e2","line":253,"updated":"2014-07-02 10:03:18.000000000","message":"An interesting question here as to whether it is the user who decides they want to go to BETA or whether ACME decides some set of projects/services/users are to be handled by BETA.  I\u0027d of thought it was the later...which doesn\u0027t jive well with this flow.  If I were BETA and I had a random flow of ACME users hitting me for projects/services/users that I was not contracted to provide resources for, I\u0027d be annoyed (with ACME).  Ideas:\n\n- ACME could use endpoint filtering to decide which projects could use BETA (and today such filtering is pretty basic)\n- Trying to think whether endpoint policy definition could also be used to define the roles need to go to BETA....however, in the above model it would be a BETA\u0027s keystone that would serve up the policy file for the resulting access to endpoints in BETA....so that doesn\u0027t really solve the problem.","commit_id":"f25492250f1f6553560255c6b947166f9ddd7d41"},{"author":{"_account_id":5707,"name":"Henry Nash","email":"henryn@linux.vnet.ibm.com","username":"henry-nash"},"change_message_id":"59d4ead21a53dc0d4ba32b9bb45b3dd1ae601b25","unresolved":false,"context_lines":[{"line_number":250,"context_line":"   (C)  ACME returns a token with one or more SPs, BETA included."},{"line_number":251,"context_line":""},{"line_number":252,"context_line":"   (D)  User scopes to a project or domain at ACME, and requests that the"},{"line_number":253,"context_line":"        BETA SP is used."},{"line_number":254,"context_line":""},{"line_number":255,"context_line":"   (E)  ACME returns a token, scoped to the requested project or domain, and"},{"line_number":256,"context_line":"        makes it usable with BETA only. The role assignments in this token"}],"source_content_type":"text/x-rst","patch_set":15,"id":"baada198_6edc4213","line":253,"in_reply_to":"baada198_0dfdac3a","updated":"2014-07-03 08:22:18.000000000","message":"So this idea doesn\u0027t affect that fact that you want to use roles as an input into the BETA federated mapping engine....it\u0027s just how you decide whether the token includes the BETA SP at all.\n\nOne idea that has been mulling for a while has been whether we extend endpoint filtering to include role based decisions (e.g. only put endpoint X in  the token if user has role Y on the project)...however there is this nagging feeling about that which is that this sounds like policy rules...and we shouldn\u0027t be distributing policy rules into other parts of the code.\n\nIf you think of the larger context, some high-level orchestration layer might want to manage these cross-SP breakouts in various ways, e.g.:\n\n- If the capacity of ACME \u003e 90%, then burst into SP (for some set of non-sensitive projects)\n- During the ACME maintenance window of 1am - 3am tonight, use SP for all services\n\nNow we don\u0027t want to encode such holistic triggers into OpenStack...but we need to ensure that we have the knobs a higher level algorithm can turn to achieve this.  None of the above examples where based on user choice....it\u0027s all down to the service providers driving the decision.","commit_id":"f25492250f1f6553560255c6b947166f9ddd7d41"},{"author":{"_account_id":1228,"name":"Joe Savak","email":"jsavak@gmail.com","username":"jsavak"},"change_message_id":"9c222f644619dab476c212ed334e9d1ffd9cc701","unresolved":false,"context_lines":[{"line_number":250,"context_line":"   (C)  ACME returns a token with one or more SPs, BETA included."},{"line_number":251,"context_line":""},{"line_number":252,"context_line":"   (D)  User scopes to a project or domain at ACME, and requests that the"},{"line_number":253,"context_line":"        BETA SP is used."},{"line_number":254,"context_line":""},{"line_number":255,"context_line":"   (E)  ACME returns a token, scoped to the requested project or domain, and"},{"line_number":256,"context_line":"        makes it usable with BETA only. The role assignments in this token"}],"source_content_type":"text/x-rst","patch_set":15,"id":"baada198_2d0a5e21","line":253,"in_reply_to":"baada198_138e62d0","updated":"2014-07-10 19:58:42.000000000","message":"+1","commit_id":"f25492250f1f6553560255c6b947166f9ddd7d41"},{"author":{"_account_id":6482,"name":"Steve Martinelli","email":"s.martinelli@gmail.com","username":"stevemar"},"change_message_id":"d929fa17786153dcc30ece458d8c6356d2613c02","unresolved":false,"context_lines":[{"line_number":250,"context_line":"   (C)  ACME returns a token with one or more SPs, BETA included."},{"line_number":251,"context_line":""},{"line_number":252,"context_line":"   (D)  User scopes to a project or domain at ACME, and requests that the"},{"line_number":253,"context_line":"        BETA SP is used."},{"line_number":254,"context_line":""},{"line_number":255,"context_line":"   (E)  ACME returns a token, scoped to the requested project or domain, and"},{"line_number":256,"context_line":"        makes it usable with BETA only. The role assignments in this token"}],"source_content_type":"text/x-rst","patch_set":15,"id":"baada198_138e62d0","line":253,"in_reply_to":"baada198_6edc4213","updated":"2014-07-04 06:03:01.000000000","message":"I think this also kind of reflects Craig\u0027s opinion, about how this approach isn\u0027t dynamic or there isn\u0027t automagic bursting happening.\n\nI think for both issues, we could enhance the client.. if some other application notices one of those conditions, then it can trigger a call to list the service providers and start firing off requests to that URL instead.","commit_id":"f25492250f1f6553560255c6b947166f9ddd7d41"},{"author":{"_account_id":8978,"name":"Marek Denis","email":"marek.denis+openstack@gmail.com","username":"marek-denis"},"change_message_id":"d886f2a4ee8f56f9eb13fcdfe539d76713282105","unresolved":false,"context_lines":[{"line_number":250,"context_line":"   (C)  ACME returns a token with one or more SPs, BETA included."},{"line_number":251,"context_line":""},{"line_number":252,"context_line":"   (D)  User scopes to a project or domain at ACME, and requests that the"},{"line_number":253,"context_line":"        BETA SP is used."},{"line_number":254,"context_line":""},{"line_number":255,"context_line":"   (E)  ACME returns a token, scoped to the requested project or domain, and"},{"line_number":256,"context_line":"        makes it usable with BETA only. The role assignments in this token"}],"source_content_type":"text/x-rst","patch_set":15,"id":"baada198_0dfdac3a","line":253,"in_reply_to":"baada198_b2afc6e2","updated":"2014-07-02 15:06:35.000000000","message":"++ for Henry\u0027s idea for filtering. However, it\u0027s relatively easy with projects/SPs and domains/SP but we were also planning to send roles and make mappings at the BETA side basin on the roles.","commit_id":"f25492250f1f6553560255c6b947166f9ddd7d41"},{"author":{"_account_id":6534,"name":"David Chadwick","email":"d.w.chadwick@truetrust.co.uk","username":"d-w-chadwick"},"change_message_id":"8e9bf0993de9dd656065dfed32514fd995194e72","unresolved":false,"context_lines":[{"line_number":264,"context_line":"        and fed into BETAs federated mapping rules, resulting in a new set of"},{"line_number":265,"context_line":"        assignments on a project or domain in BETA. BETA returns a valid token"},{"line_number":266,"context_line":"        scoped to the mapped project or domain and the respective assignments."},{"line_number":267,"context_line":""},{"line_number":268,"context_line":"Alternatives"},{"line_number":269,"context_line":"------------"},{"line_number":270,"context_line":""}],"source_content_type":"text/x-rst","patch_set":15,"id":"baada198_4756b5d3","line":267,"updated":"2014-07-02 06:17:49.000000000","message":"(H) The process can now continue recursively, and the User can learn about DELTA if it asks for an extended service catalog from BETA and has sufficient privileges to obtain this.","commit_id":"f25492250f1f6553560255c6b947166f9ddd7d41"},{"author":{"_account_id":6534,"name":"David Chadwick","email":"d.w.chadwick@truetrust.co.uk","username":"d-w-chadwick"},"change_message_id":"e8080e7c86db6484519f8091c03c5f59d03db3f1","unresolved":false,"context_lines":[{"line_number":264,"context_line":"        and fed into BETAs federated mapping rules, resulting in a new set of"},{"line_number":265,"context_line":"        assignments on a project or domain in BETA. BETA returns a valid token"},{"line_number":266,"context_line":"        scoped to the mapped project or domain and the respective assignments."},{"line_number":267,"context_line":""},{"line_number":268,"context_line":"Alternatives"},{"line_number":269,"context_line":"------------"},{"line_number":270,"context_line":""}],"source_content_type":"text/x-rst","patch_set":15,"id":"baada198_9813c30c","line":267,"in_reply_to":"baada198_3583a057","updated":"2014-07-02 11:11:36.000000000","message":"I think it is likely that BETA will treat all users from ACME in the same coarse grained way, since the provenance of where the User was actually authenticated, and where his identity attributes came from, has been lost when the SAML token from the IdP was exchanged for a Keystone token from ACME. So BETA will use the groups and roles assigned by ACME to determine the User\u0027s privileges.\n\nIf on the other hand the token contained the full provenance history of which IdP authenticated the user, and which IdPs issued the user with identity attributes (including IdP and ACME in this example) then BETA would be able to provide finer grained authorisation. However the disadvantage of this is that the token size grows each time a new keystone is added to the chain (DELTA in this example), or BETA has to have an additional message exchange with ACME to ask it for the provenance information (which gets unwieldy when you have a long chain of linked keystones such as DELTA to BETA to ACME).","commit_id":"f25492250f1f6553560255c6b947166f9ddd7d41"},{"author":{"_account_id":8978,"name":"Marek Denis","email":"marek.denis+openstack@gmail.com","username":"marek-denis"},"change_message_id":"f3add3146db2b554a849f7c0c7a46b003218c3cf","unresolved":false,"context_lines":[{"line_number":264,"context_line":"        and fed into BETAs federated mapping rules, resulting in a new set of"},{"line_number":265,"context_line":"        assignments on a project or domain in BETA. BETA returns a valid token"},{"line_number":266,"context_line":"        scoped to the mapped project or domain and the respective assignments."},{"line_number":267,"context_line":""},{"line_number":268,"context_line":"Alternatives"},{"line_number":269,"context_line":"------------"},{"line_number":270,"context_line":""}],"source_content_type":"text/x-rst","patch_set":15,"id":"baada198_3583a057","line":267,"in_reply_to":"baada198_4756b5d3","updated":"2014-07-02 10:33:44.000000000","message":"David: how would BETA decide whether user has sufficient privileges? I think it\u0027s worth mentioning.","commit_id":"f25492250f1f6553560255c6b947166f9ddd7d41"},{"author":{"_account_id":6534,"name":"David Chadwick","email":"d.w.chadwick@truetrust.co.uk","username":"d-w-chadwick"},"change_message_id":"5f411314a8816f5073f0855d3eb151eebd0cd390","unresolved":false,"context_lines":[{"line_number":264,"context_line":"        and fed into BETAs federated mapping rules, resulting in a new set of"},{"line_number":265,"context_line":"        assignments on a project or domain in BETA. BETA returns a valid token"},{"line_number":266,"context_line":"        scoped to the mapped project or domain and the respective assignments."},{"line_number":267,"context_line":""},{"line_number":268,"context_line":"Alternatives"},{"line_number":269,"context_line":"------------"},{"line_number":270,"context_line":""}],"source_content_type":"text/x-rst","patch_set":15,"id":"baada198_eb19397a","line":267,"in_reply_to":"baada198_78e98f7f","updated":"2014-07-02 17:54:54.000000000","message":"It is true that ACME produces a scoped token for BETA, and it could provide different projects/roles for different groups of users from different IdPs. But I don\u0027t think the granularity sent to BETA will ever be as fine as ACME had for itself. So there will be some loss of granularity when ACME does its attribute mappings. Then BETA has decide which of these mapped project/roles gets access to which of its resources without knowing the provenance or history of the user\u0027s authentication and identity attributes - not unless an enlarged token is transferred containing this information (as we suggest could be an optional extra in our revised mapping specs). \n\nI dont think anyone has suggested sending the original signed SAML assertion from IDP to BETA, because not even ACME has access to this (Apache consumed it and replaced it with environmental parameters). So token swapping seems to be the preferred modus operandi. The debate then focuses on what the contents of the swapped token should be.","commit_id":"f25492250f1f6553560255c6b947166f9ddd7d41"},{"author":{"_account_id":8978,"name":"Marek Denis","email":"marek.denis+openstack@gmail.com","username":"marek-denis"},"change_message_id":"3d3924254c1e47b97023c7f4c3443f71f91f4988","unresolved":false,"context_lines":[{"line_number":264,"context_line":"        and fed into BETAs federated mapping rules, resulting in a new set of"},{"line_number":265,"context_line":"        assignments on a project or domain in BETA. BETA returns a valid token"},{"line_number":266,"context_line":"        scoped to the mapped project or domain and the respective assignments."},{"line_number":267,"context_line":""},{"line_number":268,"context_line":"Alternatives"},{"line_number":269,"context_line":"------------"},{"line_number":270,"context_line":""}],"source_content_type":"text/x-rst","patch_set":15,"id":"baada198_78e98f7f","line":267,"in_reply_to":"baada198_9813c30c","updated":"2014-07-02 11:22:23.000000000","message":"@David: Why would you say BETA is not able to provide finer grained authorization? I think it does. BETA receives a scoped token issued by ACME, and by applying mapping rules it decides what token@ACME\u0027s owner can do with BETA\u0027s resources. \nBETA must also be able to distinguish which IdP authenticated the user so it can validate it\u0027s signature or even decrypt some sensitive data (for sure at least one of those two).","commit_id":"f25492250f1f6553560255c6b947166f9ddd7d41"},{"author":{"_account_id":9959,"name":"Craig A. Lee","email":"lee@aero.org","username":"craigalee"},"change_message_id":"8f56ad28c33955aa3a8f40e2d31e6f63bfcca55b","unresolved":false,"context_lines":[{"line_number":264,"context_line":"        and fed into BETAs federated mapping rules, resulting in a new set of"},{"line_number":265,"context_line":"        assignments on a project or domain in BETA. BETA returns a valid token"},{"line_number":266,"context_line":"        scoped to the mapped project or domain and the respective assignments."},{"line_number":267,"context_line":""},{"line_number":268,"context_line":"Alternatives"},{"line_number":269,"context_line":"------------"},{"line_number":270,"context_line":""}],"source_content_type":"text/x-rst","patch_set":15,"id":"baada198_f6d36ed2","line":267,"in_reply_to":"baada198_c901af06","updated":"2014-07-07 10:41:04.000000000","message":"Of course, you have fingered the exact issue that organizations like the International Grid Trust Federation came into being to address:  Whose IdPs do you trust?  For any federations to be workable, there has to be some prior agreement concerning \"Whose IdPs do you trust\".  Rather than addressing how to establish such prior agreements, at a minimum, it would be prudent to carry the authn history such that rejections can be made.  Of course, this would initially limit the scale and usefulness of federations, but presumably the market would eventually work out such issues.","commit_id":"f25492250f1f6553560255c6b947166f9ddd7d41"},{"author":{"_account_id":6534,"name":"David Chadwick","email":"d.w.chadwick@truetrust.co.uk","username":"d-w-chadwick"},"change_message_id":"ccc29c890019a635120e3f584d400cb26ba00cea","unresolved":false,"context_lines":[{"line_number":264,"context_line":"        and fed into BETAs federated mapping rules, resulting in a new set of"},{"line_number":265,"context_line":"        assignments on a project or domain in BETA. BETA returns a valid token"},{"line_number":266,"context_line":"        scoped to the mapped project or domain and the respective assignments."},{"line_number":267,"context_line":""},{"line_number":268,"context_line":"Alternatives"},{"line_number":269,"context_line":"------------"},{"line_number":270,"context_line":""}],"source_content_type":"text/x-rst","patch_set":15,"id":"baada198_c901af06","line":267,"in_reply_to":"baada198_e9212ca0","updated":"2014-07-03 18:12:50.000000000","message":"Of course this simplistic trust model allows a user from IDP2 that is untrusted by BETA, but is trusted by ACME, to still access BETA\u0027s services by authenticating via ACME rather than via BETA (as he would be rejected in the latter case).\n\nAre we happy with this being the only solution in Juno, or do we want to also have the option of allowing the authentication history to be propagated through the trust chain, so that subsequent services can reject a user if the IdP that authenticated him is not trusted by it.","commit_id":"f25492250f1f6553560255c6b947166f9ddd7d41"},{"author":{"_account_id":9959,"name":"Craig A. Lee","email":"lee@aero.org","username":"craigalee"},"change_message_id":"d16ae110ee842a8ffbbeef382d07e9075fb8795c","unresolved":false,"context_lines":[{"line_number":264,"context_line":"        and fed into BETAs federated mapping rules, resulting in a new set of"},{"line_number":265,"context_line":"        assignments on a project or domain in BETA. BETA returns a valid token"},{"line_number":266,"context_line":"        scoped to the mapped project or domain and the respective assignments."},{"line_number":267,"context_line":""},{"line_number":268,"context_line":"Alternatives"},{"line_number":269,"context_line":"------------"},{"line_number":270,"context_line":""}],"source_content_type":"text/x-rst","patch_set":15,"id":"baada198_eed75949","line":267,"in_reply_to":"baada198_e9212ca0","updated":"2014-07-03 17:47:33.000000000","message":"This is what I\u0027ve been getting at w/ the idea of federated domains.  BETA\u0027s\nAUTH_URL is associated with ACME\u0027s Domain D/Project P.  If the User is a member\nof Project P, the existing endpoint filtering is used to return a SC with BETA\u0027s\nAUTH_URL.  BETA has a corresponding Domain D\u0027 and Project P\u0027.  BETA makes its\nown local services available to members of a federation by associating those\nservice endpoints with Project P\u0027.  When a User from ACME authns to BETA for\nDomain D/D\u0027 and Project P/P\u0027, the User gets a SC that is filtered to only\ncontain those services that BETA is making available to members of that\nparticular federated domain/project.  Note that this could include things like\nDELTA\u0027s AUTH_URL.\n\nAlso note that this does not extend endpoint filtering to role-based decisions.\nEndpoint filtering is solely based on domain/project association, as it is done\nnow.  A User\u0027s roles, however, must be carried to each SP such that the local\nPEPs can make authz decisions appropriately.","commit_id":"f25492250f1f6553560255c6b947166f9ddd7d41"},{"author":{"_account_id":5707,"name":"Henry Nash","email":"henryn@linux.vnet.ibm.com","username":"henry-nash"},"change_message_id":"59d4ead21a53dc0d4ba32b9bb45b3dd1ae601b25","unresolved":false,"context_lines":[{"line_number":264,"context_line":"        and fed into BETAs federated mapping rules, resulting in a new set of"},{"line_number":265,"context_line":"        assignments on a project or domain in BETA. BETA returns a valid token"},{"line_number":266,"context_line":"        scoped to the mapped project or domain and the respective assignments."},{"line_number":267,"context_line":""},{"line_number":268,"context_line":"Alternatives"},{"line_number":269,"context_line":"------------"},{"line_number":270,"context_line":""}],"source_content_type":"text/x-rst","patch_set":15,"id":"baada198_ebe92481","line":267,"in_reply_to":"baada198_eb19397a","updated":"2014-07-03 08:22:18.000000000","message":"Agreed...I really don\u0027t think we want to be passing the (original) IdP assertion info through to BETA....otherwise why wouldn\u0027t we just have BETA  trust the original IdP?......the whole point (I thought) is that BETA shouldn\u0027t have to know anything about how the user originally authenticated themselves (to ACME)....just that they can prove that ACME has said \"they\u0027re good...and here are a set of keystone attributes that define them\".","commit_id":"f25492250f1f6553560255c6b947166f9ddd7d41"},{"author":{"_account_id":8978,"name":"Marek Denis","email":"marek.denis+openstack@gmail.com","username":"marek-denis"},"change_message_id":"1c165e858428cdc48541fc7d03f617f9c5c34448","unresolved":false,"context_lines":[{"line_number":264,"context_line":"        and fed into BETAs federated mapping rules, resulting in a new set of"},{"line_number":265,"context_line":"        assignments on a project or domain in BETA. BETA returns a valid token"},{"line_number":266,"context_line":"        scoped to the mapped project or domain and the respective assignments."},{"line_number":267,"context_line":""},{"line_number":268,"context_line":"Alternatives"},{"line_number":269,"context_line":"------------"},{"line_number":270,"context_line":""}],"source_content_type":"text/x-rst","patch_set":15,"id":"baada198_e9212ca0","line":267,"in_reply_to":"baada198_ebe92481","updated":"2014-07-03 08:35:13.000000000","message":"Henry - that\u0027s the idea.By issuing \u0027special\u0027 token ACME says: \"I authenticated him, and these are his roles, his project or domain\". Now BETA trusts ACME and doesn\u0027t really care what was the authN process. It cares about validating the token is right and issue by ACME and what\u0027s inside that token (which is now an assertion).","commit_id":"f25492250f1f6553560255c6b947166f9ddd7d41"},{"author":{"_account_id":4,"name":"Dolph Mathews","email":"dolph.mathews@gmail.com","username":"dolph"},"change_message_id":"a78960f0b88258510213c0b5aec9e246c3368e83","unresolved":false,"context_lines":[{"line_number":387,"context_line":"Notifications Impact"},{"line_number":388,"context_line":"--------------------"},{"line_number":389,"context_line":""},{"line_number":390,"context_line":"* Keystone will emit a CADF notitifcation (to authenticated and authorized identities), what"},{"line_number":391,"context_line":"  revocations should occur for previously issued assertions."},{"line_number":392,"context_line":""},{"line_number":393,"context_line":"Other End User Impact"}],"source_content_type":"text/x-rst","patch_set":15,"id":"baada198_b1c5ee3e","line":390,"updated":"2014-07-10 17:07:42.000000000","message":"notitifcation is not a thing","commit_id":"f25492250f1f6553560255c6b947166f9ddd7d41"},{"author":{"_account_id":6460,"name":"Brad Topol","email":"btopol@us.ibm.com","username":"btopol"},"change_message_id":"4ea10c108350a6ea8182c431549fa32ecf0fa9d7","unresolved":false,"context_lines":[{"line_number":40,"context_line":"This is where one Keystone trusts another to **assert federation identities"},{"line_number":41,"context_line":"to** it."},{"line_number":42,"context_line":""},{"line_number":43,"context_line":"**Use Case 1: Multiple Re-sellers:**"},{"line_number":44,"context_line":""},{"line_number":45,"context_line":"CERN has one OpenStack cloud set-up within their data"},{"line_number":46,"context_line":"center. They have Keystone sitting on top of an LDAP instance. They would"}],"source_content_type":"text/x-rst","patch_set":16,"id":"baada198_7b01db69","line":43,"updated":"2014-07-15 16:38:52.000000000","message":"Great use cases. Very well written and motivate the problem very well.","commit_id":"ba3b455309e070e8f08c51f28825f8eb05463b82"},{"author":{"_account_id":6460,"name":"Brad Topol","email":"btopol@us.ibm.com","username":"btopol"},"change_message_id":"4ea10c108350a6ea8182c431549fa32ecf0fa9d7","unresolved":false,"context_lines":[{"line_number":75,"context_line":"Requirements"},{"line_number":76,"context_line":"------------"},{"line_number":77,"context_line":""},{"line_number":78,"context_line":"1. The solution needs to be recursive, so that if Cloud A burst to Cloud B"},{"line_number":79,"context_line":"when it is overloaded, and Cloud B burst to Cloud C when it is overloaded,"},{"line_number":80,"context_line":"then jobs from A can be burst to C via B."},{"line_number":81,"context_line":""}],"source_content_type":"text/x-rst","patch_set":16,"id":"baada198_1b2fffa8","line":78,"updated":"2014-07-15 16:38:52.000000000","message":"Is this going to be supported in the Juno release?","commit_id":"ba3b455309e070e8f08c51f28825f8eb05463b82"},{"author":{"_account_id":6482,"name":"Steve Martinelli","email":"s.martinelli@gmail.com","username":"stevemar"},"change_message_id":"c9a8adcdc7782bcaffbcdafa223fe6f2111fd388","unresolved":false,"context_lines":[{"line_number":75,"context_line":"Requirements"},{"line_number":76,"context_line":"------------"},{"line_number":77,"context_line":""},{"line_number":78,"context_line":"1. The solution needs to be recursive, so that if Cloud A burst to Cloud B"},{"line_number":79,"context_line":"when it is overloaded, and Cloud B burst to Cloud C when it is overloaded,"},{"line_number":80,"context_line":"then jobs from A can be burst to C via B."},{"line_number":81,"context_line":""}],"source_content_type":"text/x-rst","patch_set":16,"id":"baada198_5e240560","line":78,"in_reply_to":"baada198_1b2fffa8","updated":"2014-07-15 16:45:28.000000000","message":"I believe it will be. When stanek, marek and myself were drawing out the interactions, it very well could work.\nI think we should make it a stretch goal, but in theory it should work.","commit_id":"ba3b455309e070e8f08c51f28825f8eb05463b82"},{"author":{"_account_id":5707,"name":"Henry Nash","email":"henryn@linux.vnet.ibm.com","username":"henry-nash"},"change_message_id":"0f8995e3a9742ddb4f97b7c8e3bc101d270a2d32","unresolved":false,"context_lines":[{"line_number":142,"context_line":"Keystone token into a SAML assertion, consumable by BETA."},{"line_number":143,"context_line":""},{"line_number":144,"context_line":"3. BETA\u0027s Keystone, upon receiving a SAML assertion will need to be able to"},{"line_number":145,"context_line":"map ACME\u0027s user to a role and group in BETA."},{"line_number":146,"context_line":""},{"line_number":147,"context_line":"::"},{"line_number":148,"context_line":""}],"source_content_type":"text/x-rst","patch_set":16,"id":"baada198_d2501660","line":145,"updated":"2014-07-15 12:24:39.000000000","message":"I might be tempted to already spill the beans as part of this sentence that this will just use the existing IceHouse SAML federation capabilities.  I think one of the nice attributes of this approach is that we are not adding any new capability for Keystone to consume federation assertions...just the ability for Keystone to generate them.  I.e. if we\u0027re happy with the security around Keystone consuming federated assertions, this change doesn\u0027t affect that security.","commit_id":"ba3b455309e070e8f08c51f28825f8eb05463b82"},{"author":{"_account_id":6460,"name":"Brad Topol","email":"btopol@us.ibm.com","username":"btopol"},"change_message_id":"4ea10c108350a6ea8182c431549fa32ecf0fa9d7","unresolved":false,"context_lines":[{"line_number":142,"context_line":"Keystone token into a SAML assertion, consumable by BETA."},{"line_number":143,"context_line":""},{"line_number":144,"context_line":"3. BETA\u0027s Keystone, upon receiving a SAML assertion will need to be able to"},{"line_number":145,"context_line":"map ACME\u0027s user to a role and group in BETA."},{"line_number":146,"context_line":""},{"line_number":147,"context_line":"::"},{"line_number":148,"context_line":""}],"source_content_type":"text/x-rst","patch_set":16,"id":"baada198_3b1be381","line":145,"in_reply_to":"baada198_5e0dece6","updated":"2014-07-15 16:38:52.000000000","message":"+1  Defintely add what Henry suggests","commit_id":"ba3b455309e070e8f08c51f28825f8eb05463b82"},{"author":{"_account_id":1228,"name":"Joe Savak","email":"jsavak@gmail.com","username":"jsavak"},"change_message_id":"86269e3b899ecf4f66e5ce451de62fceb3c3efcf","unresolved":false,"context_lines":[{"line_number":142,"context_line":"Keystone token into a SAML assertion, consumable by BETA."},{"line_number":143,"context_line":""},{"line_number":144,"context_line":"3. BETA\u0027s Keystone, upon receiving a SAML assertion will need to be able to"},{"line_number":145,"context_line":"map ACME\u0027s user to a role and group in BETA."},{"line_number":146,"context_line":""},{"line_number":147,"context_line":"::"},{"line_number":148,"context_line":""}],"source_content_type":"text/x-rst","patch_set":16,"id":"baada198_5e0dece6","line":145,"in_reply_to":"baada198_d2501660","updated":"2014-07-15 14:15:13.000000000","message":"+1.","commit_id":"ba3b455309e070e8f08c51f28825f8eb05463b82"},{"author":{"_account_id":6482,"name":"Steve Martinelli","email":"s.martinelli@gmail.com","username":"stevemar"},"change_message_id":"c9a8adcdc7782bcaffbcdafa223fe6f2111fd388","unresolved":false,"context_lines":[{"line_number":142,"context_line":"Keystone token into a SAML assertion, consumable by BETA."},{"line_number":143,"context_line":""},{"line_number":144,"context_line":"3. BETA\u0027s Keystone, upon receiving a SAML assertion will need to be able to"},{"line_number":145,"context_line":"map ACME\u0027s user to a role and group in BETA."},{"line_number":146,"context_line":""},{"line_number":147,"context_line":"::"},{"line_number":148,"context_line":""}],"source_content_type":"text/x-rst","patch_set":16,"id":"baada198_4fe618b1","line":145,"in_reply_to":"baada198_d2501660","updated":"2014-07-15 16:45:28.000000000","message":"How about I add a note before 3:\n\n  Resume previously established Icehouse federation behaviour","commit_id":"ba3b455309e070e8f08c51f28825f8eb05463b82"},{"author":{"_account_id":6460,"name":"Brad Topol","email":"btopol@us.ibm.com","username":"btopol"},"change_message_id":"4ea10c108350a6ea8182c431549fa32ecf0fa9d7","unresolved":false,"context_lines":[{"line_number":148,"context_line":""},{"line_number":149,"context_line":"            Figure 1: Creating a trust relationship"},{"line_number":150,"context_line":""},{"line_number":151,"context_line":"     +----------+                                 +---------------+"},{"line_number":152,"context_line":"     |          |\u003c---(A)-- Add BETA as an SP  ----|               |"},{"line_number":153,"context_line":"     |   ACME   |                                 |  ACME Cloud   |"},{"line_number":154,"context_line":"     |          |                                 |  Implementer  |"}],"source_content_type":"text/x-rst","patch_set":16,"id":"baada198_fb008b04","line":151,"updated":"2014-07-15 16:38:52.000000000","message":"Great picture","commit_id":"ba3b455309e070e8f08c51f28825f8eb05463b82"},{"author":{"_account_id":6482,"name":"Steve Martinelli","email":"s.martinelli@gmail.com","username":"stevemar"},"change_message_id":"c9a8adcdc7782bcaffbcdafa223fe6f2111fd388","unresolved":false,"context_lines":[{"line_number":148,"context_line":""},{"line_number":149,"context_line":"            Figure 1: Creating a trust relationship"},{"line_number":150,"context_line":""},{"line_number":151,"context_line":"     +----------+                                 +---------------+"},{"line_number":152,"context_line":"     |          |\u003c---(A)-- Add BETA as an SP  ----|               |"},{"line_number":153,"context_line":"     |   ACME   |                                 |  ACME Cloud   |"},{"line_number":154,"context_line":"     |          |                                 |  Implementer  |"}],"source_content_type":"text/x-rst","patch_set":16,"id":"baada198_5edb254f","line":151,"in_reply_to":"baada198_fb008b04","updated":"2014-07-15 16:45:28.000000000","message":"thanks! I think they are neat too","commit_id":"ba3b455309e070e8f08c51f28825f8eb05463b82"},{"author":{"_account_id":8978,"name":"Marek Denis","email":"marek.denis+openstack@gmail.com","username":"marek-denis"},"change_message_id":"736a18407372a04e51e5fca29a7b7194109dde6e","unresolved":false,"context_lines":[{"line_number":236,"context_line":""},{"line_number":237,"context_line":"   (D)  ACME cloud returns the a SAML assertion."},{"line_number":238,"context_line":""},{"line_number":239,"context_line":"   Resumes normal Icehouse behaviour:"},{"line_number":240,"context_line":""},{"line_number":241,"context_line":"   (E)  User authenticates with BETA, presenting the SAML assertion returned"},{"line_number":242,"context_line":"        from (D)."}],"source_content_type":"text/x-rst","patch_set":16,"id":"baada198_42443f46","line":239,"updated":"2014-07-15 09:07:19.000000000","message":"I would make clear that we mean here \u0027Icehouse federation\u0027, or even SAML based federation workflow.","commit_id":"ba3b455309e070e8f08c51f28825f8eb05463b82"},{"author":{"_account_id":1228,"name":"Joe Savak","email":"jsavak@gmail.com","username":"jsavak"},"change_message_id":"86269e3b899ecf4f66e5ce451de62fceb3c3efcf","unresolved":false,"context_lines":[{"line_number":236,"context_line":""},{"line_number":237,"context_line":"   (D)  ACME cloud returns the a SAML assertion."},{"line_number":238,"context_line":""},{"line_number":239,"context_line":"   Resumes normal Icehouse behaviour:"},{"line_number":240,"context_line":""},{"line_number":241,"context_line":"   (E)  User authenticates with BETA, presenting the SAML assertion returned"},{"line_number":242,"context_line":"        from (D)."}],"source_content_type":"text/x-rst","patch_set":16,"id":"baada198_1e2e1443","line":239,"in_reply_to":"baada198_42443f46","updated":"2014-07-15 14:15:13.000000000","message":"+1","commit_id":"ba3b455309e070e8f08c51f28825f8eb05463b82"},{"author":{"_account_id":6482,"name":"Steve Martinelli","email":"s.martinelli@gmail.com","username":"stevemar"},"change_message_id":"c9a8adcdc7782bcaffbcdafa223fe6f2111fd388","unresolved":false,"context_lines":[{"line_number":236,"context_line":""},{"line_number":237,"context_line":"   (D)  ACME cloud returns the a SAML assertion."},{"line_number":238,"context_line":""},{"line_number":239,"context_line":"   Resumes normal Icehouse behaviour:"},{"line_number":240,"context_line":""},{"line_number":241,"context_line":"   (E)  User authenticates with BETA, presenting the SAML assertion returned"},{"line_number":242,"context_line":"        from (D)."}],"source_content_type":"text/x-rst","patch_set":16,"id":"baada198_2ff3a473","line":239,"in_reply_to":"baada198_42443f46","updated":"2014-07-15 16:45:28.000000000","message":"how about:\n\n  Resume previously established Icehouse federation behaviour","commit_id":"ba3b455309e070e8f08c51f28825f8eb05463b82"},{"author":{"_account_id":5707,"name":"Henry Nash","email":"henryn@linux.vnet.ibm.com","username":"henry-nash"},"change_message_id":"0f8995e3a9742ddb4f97b7c8e3bc101d270a2d32","unresolved":false,"context_lines":[{"line_number":300,"context_line":"* If the IdP deletes the SP, then the SP should delete the IdP as well. This"},{"line_number":301,"context_line":"  is an out-of-band operation, and beyond the scope of this specification."},{"line_number":302,"context_line":""},{"line_number":303,"context_line":"* Possible information leakage. The token could contain a catalog, roles, etc."},{"line_number":304,"context_line":"  from ACME and that information is available to BETA. Though the information"},{"line_number":305,"context_line":"  may not be important at the moment, it could be important in the future."},{"line_number":306,"context_line":""}],"source_content_type":"text/x-rst","patch_set":16,"id":"baada198_92369e4f","line":303,"updated":"2014-07-15 12:24:39.000000000","message":"I don\u0027t think this is true any more is it......I doubt we\u0027ll transform the catalog into SAML assertions....","commit_id":"ba3b455309e070e8f08c51f28825f8eb05463b82"},{"author":{"_account_id":8978,"name":"Marek Denis","email":"marek.denis+openstack@gmail.com","username":"marek-denis"},"change_message_id":"33b12183d35d9499cf494801aa9a50ca5c557027","unresolved":false,"context_lines":[{"line_number":300,"context_line":"* If the IdP deletes the SP, then the SP should delete the IdP as well. This"},{"line_number":301,"context_line":"  is an out-of-band operation, and beyond the scope of this specification."},{"line_number":302,"context_line":""},{"line_number":303,"context_line":"* Possible information leakage. The token could contain a catalog, roles, etc."},{"line_number":304,"context_line":"  from ACME and that information is available to BETA. Though the information"},{"line_number":305,"context_line":"  may not be important at the moment, it could be important in the future."},{"line_number":306,"context_line":""}],"source_content_type":"text/x-rst","patch_set":16,"id":"baada198_b869c3bf","line":303,"in_reply_to":"baada198_92369e4f","updated":"2014-07-15 12:54:36.000000000","message":"yeah, remove catalog.","commit_id":"ba3b455309e070e8f08c51f28825f8eb05463b82"},{"author":{"_account_id":6482,"name":"Steve Martinelli","email":"s.martinelli@gmail.com","username":"stevemar"},"change_message_id":"c9a8adcdc7782bcaffbcdafa223fe6f2111fd388","unresolved":false,"context_lines":[{"line_number":300,"context_line":"* If the IdP deletes the SP, then the SP should delete the IdP as well. This"},{"line_number":301,"context_line":"  is an out-of-band operation, and beyond the scope of this specification."},{"line_number":302,"context_line":""},{"line_number":303,"context_line":"* Possible information leakage. The token could contain a catalog, roles, etc."},{"line_number":304,"context_line":"  from ACME and that information is available to BETA. Though the information"},{"line_number":305,"context_line":"  may not be important at the moment, it could be important in the future."},{"line_number":306,"context_line":""}],"source_content_type":"text/x-rst","patch_set":16,"id":"baada198_4fcff828","line":303,"in_reply_to":"baada198_b869c3bf","updated":"2014-07-15 16:45:28.000000000","message":"I\u0027ll remove catalog","commit_id":"ba3b455309e070e8f08c51f28825f8eb05463b82"},{"author":{"_account_id":5707,"name":"Henry Nash","email":"henryn@linux.vnet.ibm.com","username":"henry-nash"},"change_message_id":"0f8995e3a9742ddb4f97b7c8e3bc101d270a2d32","unresolved":false,"context_lines":[{"line_number":326,"context_line":""},{"line_number":327,"context_line":"The following operations may impact performance:"},{"line_number":328,"context_line":""},{"line_number":329,"context_line":"* A potentially larger catalog contains more data to send and sift through."},{"line_number":330,"context_line":""},{"line_number":331,"context_line":"* More certificates to validate tokens against."},{"line_number":332,"context_line":""}],"source_content_type":"text/x-rst","patch_set":16,"id":"baada198_f2743aff","line":329,"updated":"2014-07-15 12:24:39.000000000","message":"Will it be significantly larger?  Aren\u0027t we saying that it will just have an authentication endpoint per SP that you trust?","commit_id":"ba3b455309e070e8f08c51f28825f8eb05463b82"},{"author":{"_account_id":5707,"name":"Henry Nash","email":"henryn@linux.vnet.ibm.com","username":"henry-nash"},"change_message_id":"2842535c6ed72d99c32261eda4de096b892cb00a","unresolved":false,"context_lines":[{"line_number":326,"context_line":""},{"line_number":327,"context_line":"The following operations may impact performance:"},{"line_number":328,"context_line":""},{"line_number":329,"context_line":"* A potentially larger catalog contains more data to send and sift through."},{"line_number":330,"context_line":""},{"line_number":331,"context_line":"* More certificates to validate tokens against."},{"line_number":332,"context_line":""}],"source_content_type":"text/x-rst","patch_set":16,"id":"baada198_f3b6fc3c","line":329,"in_reply_to":"baada198_b897038f","updated":"2014-07-15 13:12:35.000000000","message":"fair comment.","commit_id":"ba3b455309e070e8f08c51f28825f8eb05463b82"},{"author":{"_account_id":8978,"name":"Marek Denis","email":"marek.denis+openstack@gmail.com","username":"marek-denis"},"change_message_id":"33b12183d35d9499cf494801aa9a50ca5c557027","unresolved":false,"context_lines":[{"line_number":326,"context_line":""},{"line_number":327,"context_line":"The following operations may impact performance:"},{"line_number":328,"context_line":""},{"line_number":329,"context_line":"* A potentially larger catalog contains more data to send and sift through."},{"line_number":330,"context_line":""},{"line_number":331,"context_line":"* More certificates to validate tokens against."},{"line_number":332,"context_line":""}],"source_content_type":"text/x-rst","patch_set":16,"id":"baada198_b897038f","line":329,"in_reply_to":"baada198_f2743aff","updated":"2014-07-15 12:54:36.000000000","message":"I think Having 50 or 100 trusted SPs will make it significantly bigger, so I would keep this sentence.","commit_id":"ba3b455309e070e8f08c51f28825f8eb05463b82"},{"author":{"_account_id":1228,"name":"Joe Savak","email":"jsavak@gmail.com","username":"jsavak"},"change_message_id":"86269e3b899ecf4f66e5ce451de62fceb3c3efcf","unresolved":false,"context_lines":[{"line_number":326,"context_line":""},{"line_number":327,"context_line":"The following operations may impact performance:"},{"line_number":328,"context_line":""},{"line_number":329,"context_line":"* A potentially larger catalog contains more data to send and sift through."},{"line_number":330,"context_line":""},{"line_number":331,"context_line":"* More certificates to validate tokens against."},{"line_number":332,"context_line":""}],"source_content_type":"text/x-rst","patch_set":16,"id":"baada198_fed320fe","line":329,"in_reply_to":"baada198_f3b6fc3c","updated":"2014-07-15 14:15:13.000000000","message":"This kind of performance impact exists today for the most part. A catalog can be pretty large with the endpoints that as user has access to. The service providers that a user can request access to is much like an endpoint represented in the catalog.","commit_id":"ba3b455309e070e8f08c51f28825f8eb05463b82"},{"author":{"_account_id":6482,"name":"Steve Martinelli","email":"s.martinelli@gmail.com","username":"stevemar"},"change_message_id":"c9a8adcdc7782bcaffbcdafa223fe6f2111fd388","unresolved":false,"context_lines":[{"line_number":326,"context_line":""},{"line_number":327,"context_line":"The following operations may impact performance:"},{"line_number":328,"context_line":""},{"line_number":329,"context_line":"* A potentially larger catalog contains more data to send and sift through."},{"line_number":330,"context_line":""},{"line_number":331,"context_line":"* More certificates to validate tokens against."},{"line_number":332,"context_line":""}],"source_content_type":"text/x-rst","patch_set":16,"id":"baada198_be6c419f","line":329,"in_reply_to":"baada198_fed320fe","updated":"2014-07-15 16:45:28.000000000","message":"that\u0027s also true, i\u0027ll combine all these points.","commit_id":"ba3b455309e070e8f08c51f28825f8eb05463b82"},{"author":{"_account_id":6460,"name":"Brad Topol","email":"btopol@us.ibm.com","username":"btopol"},"change_message_id":"56ad4ac9a02af257cae55fd2965b0a88e41b5f45","unresolved":false,"context_lines":[{"line_number":141,"context_line":"Once ACME\u0027s users have authenticated with ACME, they may transform their"},{"line_number":142,"context_line":"Keystone token into a SAML assertion, consumable by BETA."},{"line_number":143,"context_line":""},{"line_number":144,"context_line":"Resume previously established Icehouse federation behaviour:"},{"line_number":145,"context_line":""},{"line_number":146,"context_line":"3. BETA\u0027s Keystone, upon receiving a SAML assertion will need to be able to"},{"line_number":147,"context_line":"map ACME\u0027s user to a role and group in BETA."}],"source_content_type":"text/x-rst","patch_set":17,"id":"baada198_3f2908f3","line":144,"updated":"2014-07-15 19:12:26.000000000","message":"Hate this line. Its confusing and doesn\u0027t make clear what Henry was asking you to point out. I\u0027d  rather have this line removed than have it there.\n\nHow about:\n\nIt is worth noting that this new capability is built on and leverages the existing Icehouse SAML federation capabilites. As such it does not require modifications to Keystone\u0027s existing ability to consume federation assertions.  Instead it just adds the ability for Keystone to generate assertions in addition to consuming them.","commit_id":"e5baf838f026dec31234ead80aea61b78b13eb1b"},{"author":{"_account_id":6534,"name":"David Chadwick","email":"d.w.chadwick@truetrust.co.uk","username":"d-w-chadwick"},"change_message_id":"5031d75f98f157aac19f961ebba635688126f38d","unresolved":false,"context_lines":[{"line_number":237,"context_line":""},{"line_number":238,"context_line":"   (B)  User is returned a service catalog with ACME\u0027s services as well"},{"line_number":239,"context_line":"        as URLs he can access from trusted service providers."},{"line_number":240,"context_line":""},{"line_number":241,"context_line":"   (C)  User will send his scoped token, and \"BETA\" (a region ID) to ACME."},{"line_number":242,"context_line":""},{"line_number":243,"context_line":"   (D)  ACME cloud returns the a SAML assertion."}],"source_content_type":"text/x-rst","patch_set":19,"id":"baada198_bddb4720","line":240,"updated":"2014-07-16 11:35:59.000000000","message":"as URLs of the Keystone services of trusted service providers.","commit_id":"7b0dd0967e1d40dc2d52b289e763a4879a5d506b"},{"author":{"_account_id":6534,"name":"David Chadwick","email":"d.w.chadwick@truetrust.co.uk","username":"d-w-chadwick"},"change_message_id":"5031d75f98f157aac19f961ebba635688126f38d","unresolved":false,"context_lines":[{"line_number":241,"context_line":"   (C)  User will send his scoped token, and \"BETA\" (a region ID) to ACME."},{"line_number":242,"context_line":""},{"line_number":243,"context_line":"   (D)  ACME cloud returns the a SAML assertion."},{"line_number":244,"context_line":""},{"line_number":245,"context_line":"   Resume previously established Icehouse federation behaviour:"},{"line_number":246,"context_line":""},{"line_number":247,"context_line":"   (E)  User authenticates with BETA, presenting the SAML assertion returned"}],"source_content_type":"text/x-rst","patch_set":19,"id":"baada198_7dfa8f44","line":244,"updated":"2014-07-16 11:35:59.000000000","message":"Note. User has to know the URL of the Keystone service of BETA, so this should be sent in step B.","commit_id":"7b0dd0967e1d40dc2d52b289e763a4879a5d506b"},{"author":{"_account_id":6534,"name":"David Chadwick","email":"d.w.chadwick@truetrust.co.uk","username":"d-w-chadwick"},"change_message_id":"5031d75f98f157aac19f961ebba635688126f38d","unresolved":false,"context_lines":[{"line_number":246,"context_line":""},{"line_number":247,"context_line":"   (E)  User authenticates with BETA, presenting the SAML assertion returned"},{"line_number":248,"context_line":"        from (D)."},{"line_number":249,"context_line":""},{"line_number":250,"context_line":"   (F)  BETA receives the SAML assertion and resumes the established federation"},{"line_number":251,"context_line":"        authenticaion flow."},{"line_number":252,"context_line":""}],"source_content_type":"text/x-rst","patch_set":19,"id":"baada198_fd421f67","line":249,"updated":"2014-07-16 11:35:59.000000000","message":"Note. ACME is now acting as a trusted proxy IdP, and the history of where the user actually authenticated (IdP) may be lost to BETA, depending upon what the SAML assertion contains.","commit_id":"7b0dd0967e1d40dc2d52b289e763a4879a5d506b"},{"author":{"_account_id":6534,"name":"David Chadwick","email":"d.w.chadwick@truetrust.co.uk","username":"d-w-chadwick"},"change_message_id":"5031d75f98f157aac19f961ebba635688126f38d","unresolved":false,"context_lines":[{"line_number":302,"context_line":""},{"line_number":303,"context_line":"* If the SP (BETA) wishes to no longer accept requests from the IdP, the SP admin"},{"line_number":304,"context_line":"  can simply disable the ACME IdP entry."},{"line_number":305,"context_line":""},{"line_number":306,"context_line":"* If the IdP deletes the SP, then the SP should delete the IdP as well. This"},{"line_number":307,"context_line":"  is an out-of-band operation, and beyond the scope of this specification."},{"line_number":308,"context_line":""}],"source_content_type":"text/x-rst","patch_set":19,"id":"baada198_a82f8787","line":305,"updated":"2014-07-16 11:35:59.000000000","message":"How does BETA know that ACME used IdP for user authentication and not IdP2? Is this information transferred to BETA in the SAML assertion?\n\nWhat if ACME trusts and uses IDP1, IDP2 and IDP3 and BETA only trusts IDP1 and IDP2? How is IDP3 to be ruled out?","commit_id":"7b0dd0967e1d40dc2d52b289e763a4879a5d506b"},{"author":{"_account_id":6534,"name":"David Chadwick","email":"d.w.chadwick@truetrust.co.uk","username":"d-w-chadwick"},"change_message_id":"5031d75f98f157aac19f961ebba635688126f38d","unresolved":false,"context_lines":[{"line_number":309,"context_line":"* Possible information leakage. The token could contain IDs and roles, etc."},{"line_number":310,"context_line":"  from ACME and that information is available to BETA. Though the information"},{"line_number":311,"context_line":"  may not be important at the moment, it could be important in the future."},{"line_number":312,"context_line":""},{"line_number":313,"context_line":"* Does this increase the surface area of an attack if a cloud is compromised?"},{"line_number":314,"context_line":"  For example, say ACME has a partnership with BETA and DELTA as SPs."},{"line_number":315,"context_line":"  A compromise of BETA is a Compromise of ACME and DELTA at the token level."}],"source_content_type":"text/x-rst","patch_set":19,"id":"baada198_08987369","line":312,"updated":"2014-07-16 11:35:59.000000000","message":"The SAML assertion has to contain some identity information of the user, otherwise it cannot be used by BETA. There are several choices here\n\n1. Only send the original identity information from the authenticating IDP\n\n2. Only send the mapped identity information from the proxy IdP.\n\n3. Send both lots of information\n\nWhich one is going to be chosen? The answer is that it depends upon your trust model. If your trust model is, we fully trust proxy IDPs and dont care about the provenance or history of authentication, then only send 2. above. If your trust model is, we dont trust intermediate proxies and want the original identity information signed by the original IDP, then send 1. above. If your trust model is we trust proxy IdPs but would like them to also send us history information, then use 3 above.","commit_id":"7b0dd0967e1d40dc2d52b289e763a4879a5d506b"},{"author":{"_account_id":6534,"name":"David Chadwick","email":"d.w.chadwick@truetrust.co.uk","username":"d-w-chadwick"},"change_message_id":"5031d75f98f157aac19f961ebba635688126f38d","unresolved":false,"context_lines":[{"line_number":315,"context_line":"  A compromise of BETA is a Compromise of ACME and DELTA at the token level."},{"line_number":316,"context_line":""},{"line_number":317,"context_line":"  * This will no longer be an issue since SAML assertions are X509 signed."},{"line_number":318,"context_line":""},{"line_number":319,"context_line":"Notifications Impact"},{"line_number":320,"context_line":"--------------------"},{"line_number":321,"context_line":""}],"source_content_type":"text/x-rst","patch_set":19,"id":"baada198_6872cfe4","line":318,"updated":"2014-07-16 11:35:59.000000000","message":"this depends upon the type of SAML assertion being used. If it is an untargeted bearer token, then BETA could use the user\u0027s token to access DELTA.","commit_id":"7b0dd0967e1d40dc2d52b289e763a4879a5d506b"},{"author":{"_account_id":6534,"name":"David Chadwick","email":"d.w.chadwick@truetrust.co.uk","username":"d-w-chadwick"},"change_message_id":"07c0b9fcf2cc524721071cc6b1846872715fcb68","unresolved":false,"context_lines":[{"line_number":35,"context_line":"and Keystone. This allowed Cloud Implementers to set-up single-sign-on when"},{"line_number":36,"context_line":"configuring their cloud and not incur the administrative overhead that comes"},{"line_number":37,"context_line":"with provisioning identities in Keystone. Keystone trusts the IdP enough to"},{"line_number":38,"context_line":"**accept federated identities from** them. However, there is no way right now"},{"line_number":39,"context_line":"for one Keystone to trust another Keystone. This is where one Keystone trusts"},{"line_number":40,"context_line":"another to **assert federation identities to** it."},{"line_number":41,"context_line":""}],"source_content_type":"text/x-rst","patch_set":20,"id":"baada198_f51e88ba","line":38,"updated":"2014-07-17 09:41:18.000000000","message":"from it","commit_id":"132406aadebc317b417edc860bbb53f50210a57c"},{"author":{"_account_id":6534,"name":"David Chadwick","email":"d.w.chadwick@truetrust.co.uk","username":"d-w-chadwick"},"change_message_id":"07c0b9fcf2cc524721071cc6b1846872715fcb68","unresolved":false,"context_lines":[{"line_number":128,"context_line":"Proposed Change"},{"line_number":129,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":130,"context_line":""},{"line_number":131,"context_line":"1. Establish a trust between the both entities. BETA, the trusted service"},{"line_number":132,"context_line":"   provider is an external service (likely another Keystone), which trusts the"},{"line_number":133,"context_line":"   local Keystone to **assert federated identities to** it."},{"line_number":134,"context_line":""}],"source_content_type":"text/x-rst","patch_set":20,"id":"baada198_f5fa0842","line":131,"updated":"2014-07-17 09:41:18.000000000","message":"between both Keystones.","commit_id":"132406aadebc317b417edc860bbb53f50210a57c"},{"author":{"_account_id":6534,"name":"David Chadwick","email":"d.w.chadwick@truetrust.co.uk","username":"d-w-chadwick"},"change_message_id":"07c0b9fcf2cc524721071cc6b1846872715fcb68","unresolved":false,"context_lines":[{"line_number":148,"context_line":"   modifications to Keystone\u0027s existing ability to consume federation"},{"line_number":149,"context_line":"   assertions. Instead it just adds the ability for Keystone to generate"},{"line_number":150,"context_line":"   assertions in addition to consuming them."},{"line_number":151,"context_line":""},{"line_number":152,"context_line":"3. BETA\u0027s Keystone, upon receiving a SAML assertion will need to be able to map"},{"line_number":153,"context_line":"   ACME\u0027s user to a role and group in BETA."},{"line_number":154,"context_line":""}],"source_content_type":"text/x-rst","patch_set":20,"id":"baada198_980bc323","line":151,"updated":"2014-07-17 09:41:18.000000000","message":"It is also worth noting that the Icehouse release put all the SAML handling into the Apache front end so that Keystone did not need to be burdened with supporting SAML libraries. By making Keystone a SAML IdP, the very libraries that were wished to be excluded in Icehouse will now be introduced into Juno. In which case, it negates the need to have an Apache front end to accept SAML assertions, as the Keystone SAML libraries will be able to validate them itself. In this way, it should be possible in Juno to run Keystone without an Apache front end and still support the SAML federation protocol.","commit_id":"132406aadebc317b417edc860bbb53f50210a57c"},{"author":{"_account_id":9959,"name":"Craig A. Lee","email":"lee@aero.org","username":"craigalee"},"change_message_id":"406dd0e06592d52d1fd2aae0c931870f60f9913d","unresolved":false,"context_lines":[{"line_number":150,"context_line":"   assertions in addition to consuming them."},{"line_number":151,"context_line":""},{"line_number":152,"context_line":"3. BETA\u0027s Keystone, upon receiving a SAML assertion will need to be able to map"},{"line_number":153,"context_line":"   ACME\u0027s user to a role and group in BETA."},{"line_number":154,"context_line":""},{"line_number":155,"context_line":"::"},{"line_number":156,"context_line":""}],"source_content_type":"text/x-rst","patch_set":20,"id":"baada198_84eb35db","line":153,"updated":"2014-07-18 06:26:56.000000000","message":"In so far as a group is associated with a domain or project, this might work, but a user doesn\u0027t necessarily have to be part of a group.  The main thing is that when doing domain or project authentication in ACME, the User has a set of roles that are subsequently used to decide authorizations.  When BETA receives the SAML assertion, I would think that BETA would have to map the User to a domain or project that somehow \"means the right thing\".  In Use Case #4, for example, the User should only be allowed to allocate storage containers.  Hence, the SC returned would be filtered to not include Nova endpoints, etc.  Knowing how to map SAML assertions to domains/projects could be done by out-of-band coordination.  This is what I\u0027m using the term \"federated domains\" for -- SPs providers know what a User\u0027s authorizations are based on which domain they originally authenticated for.","commit_id":"132406aadebc317b417edc860bbb53f50210a57c"},{"author":{"_account_id":9959,"name":"Craig A. Lee","email":"lee@aero.org","username":"craigalee"},"change_message_id":"406dd0e06592d52d1fd2aae0c931870f60f9913d","unresolved":false,"context_lines":[{"line_number":237,"context_line":"2. User is returned a service catalog with ACME\u0027s services as well as URLs of"},{"line_number":238,"context_line":"   the identity services of trusted service providers."},{"line_number":239,"context_line":""},{"line_number":240,"context_line":"3. User will send his scoped token, and \"BETA\" (a region ID) to ACME."},{"line_number":241,"context_line":""},{"line_number":242,"context_line":"4. ACME cloud returns the a SAML assertion."},{"line_number":243,"context_line":""}],"source_content_type":"text/x-rst","patch_set":20,"id":"baada198_a4b919ee","line":240,"updated":"2014-07-18 06:26:56.000000000","message":"Is \"region ID\" the right concept here?  I thought regions were regions of deployment, meaning that they were different geographical regions but essentially under control of the same Keystone, i.e., part of the same administrative domain where they weren\u0027t any trust issues.  Wouldn\u0027t BETA have to have a \"Trusted SP ID\" with the auth_url as part of the service catalog?","commit_id":"132406aadebc317b417edc860bbb53f50210a57c"},{"author":{"_account_id":5046,"name":"Lance Bragstad","email":"lbragstad@redhat.com","username":"ldbragst"},"change_message_id":"7d5436d4f5a0d5efeef600cc6efac6c489b983cc","unresolved":false,"context_lines":[{"line_number":239,"context_line":""},{"line_number":240,"context_line":"3. User will send his scoped token, and \"BETA\" (a region ID) to ACME."},{"line_number":241,"context_line":""},{"line_number":242,"context_line":"4. ACME cloud returns the a SAML assertion."},{"line_number":243,"context_line":""},{"line_number":244,"context_line":"Resume previously established Icehouse federation behaviour:"},{"line_number":245,"context_line":""}],"source_content_type":"text/x-rst","patch_set":20,"id":"baada198_a0c49060","line":242,"updated":"2014-07-18 16:09:14.000000000","message":"nit: rm the*","commit_id":"132406aadebc317b417edc860bbb53f50210a57c"},{"author":{"_account_id":6534,"name":"David Chadwick","email":"d.w.chadwick@truetrust.co.uk","username":"d-w-chadwick"},"change_message_id":"07c0b9fcf2cc524721071cc6b1846872715fcb68","unresolved":false,"context_lines":[{"line_number":240,"context_line":"3. User will send his scoped token, and \"BETA\" (a region ID) to ACME."},{"line_number":241,"context_line":""},{"line_number":242,"context_line":"4. ACME cloud returns the a SAML assertion."},{"line_number":243,"context_line":""},{"line_number":244,"context_line":"Resume previously established Icehouse federation behaviour:"},{"line_number":245,"context_line":""},{"line_number":246,"context_line":"5. User authenticates with BETA, presenting the SAML assertion returned from"}],"source_content_type":"text/x-rst","patch_set":20,"id":"baada198_58068b86","line":243,"updated":"2014-07-17 09:41:18.000000000","message":"ACME returns a SAML assertion","commit_id":"132406aadebc317b417edc860bbb53f50210a57c"},{"author":{"_account_id":6534,"name":"David Chadwick","email":"d.w.chadwick@truetrust.co.uk","username":"d-w-chadwick"},"change_message_id":"55c6c41faaf1ebbbae87b84863a3954d5c897be1","unresolved":false,"context_lines":[{"line_number":247,"context_line":"   (4). Note that because ACME is acting as a trusted proxy to the user\u0027s IdP,"},{"line_number":248,"context_line":"   the history of where the user actually authenticated (the user\u0027s IdP) may be"},{"line_number":249,"context_line":"   lost to BETA, unless it is specifically identified in the SAML assertion."},{"line_number":250,"context_line":""},{"line_number":251,"context_line":"6. BETA receives the SAML assertion and resumes the established federation"},{"line_number":252,"context_line":"   authenticaion flow."},{"line_number":253,"context_line":""}],"source_content_type":"text/x-rst","patch_set":20,"id":"baada198_21794d93","line":250,"updated":"2014-07-19 17:28:57.000000000","message":"This can be achieved by including the original signed SAML assertion from the user\u0027s IdP in message (4) as one of the user\u0027s identity attributes. In this way BETA does not need to trust ACME as a proxy IdP since it will have access to the original signed assertion from IdP, and can make its own trust decisions about the way the user was authenticated and identified.","commit_id":"132406aadebc317b417edc860bbb53f50210a57c"},{"author":{"_account_id":6534,"name":"David Chadwick","email":"d.w.chadwick@truetrust.co.uk","username":"d-w-chadwick"},"change_message_id":"07c0b9fcf2cc524721071cc6b1846872715fcb68","unresolved":false,"context_lines":[{"line_number":274,"context_line":"3. Each CSP hosts a local token exchange service (which could be Keystone) so"},{"line_number":275,"context_line":"   that when users land at the CSP then whatever credential they currently hold"},{"line_number":276,"context_line":"   can be exchanged for the local one used by the CSP\u0027s services."},{"line_number":277,"context_line":""},{"line_number":278,"context_line":"   This is a workable model if Keystone becomes the local token exchange"},{"line_number":279,"context_line":"   service. None of the CSP\u0027s services need to change. If the user hits"},{"line_number":280,"context_line":"   Keystone first it will simply exchange the remote token for a local one and"}],"source_content_type":"text/x-rst","patch_set":20,"id":"baada198_98a10349","line":277,"updated":"2014-07-17 09:41:18.000000000","message":"Note. This appears to be the model that is now being suggested, with SAML being the standard token format for use between CSPs.","commit_id":"132406aadebc317b417edc860bbb53f50210a57c"},{"author":{"_account_id":6534,"name":"David Chadwick","email":"d.w.chadwick@truetrust.co.uk","username":"d-w-chadwick"},"change_message_id":"07c0b9fcf2cc524721071cc6b1846872715fcb68","unresolved":false,"context_lines":[{"line_number":307,"context_line":"* If the IdP deletes the SP, then the SP should delete the IdP as well. This is"},{"line_number":308,"context_line":"  an out-of-band operation, and beyond the scope of this specification."},{"line_number":309,"context_line":""},{"line_number":310,"context_line":"* Possible information leakage. The token could contain IDs and roles, etc."},{"line_number":311,"context_line":"  from ACME and that information is available to BETA. Though the information"},{"line_number":312,"context_line":"  may not be important at the moment, it could be important in the future."},{"line_number":313,"context_line":""}],"source_content_type":"text/x-rst","patch_set":20,"id":"baada198_584ccb9d","line":310,"updated":"2014-07-17 09:41:18.000000000","message":"I would say The token must contain IDs and roles etc....(otherwise the user cannot be authorised to access BETA)","commit_id":"132406aadebc317b417edc860bbb53f50210a57c"},{"author":{"_account_id":5046,"name":"Lance Bragstad","email":"lbragstad@redhat.com","username":"ldbragst"},"change_message_id":"7d5436d4f5a0d5efeef600cc6efac6c489b983cc","unresolved":false,"context_lines":[{"line_number":313,"context_line":""},{"line_number":314,"context_line":"* Does this increase the surface area of an attack if a cloud is compromised?"},{"line_number":315,"context_line":"  For example, say ACME has a partnership with BETA and DELTA as SPs. A"},{"line_number":316,"context_line":"  compromise of BETA is a Compromise of ACME and DELTA at the token level."},{"line_number":317,"context_line":""},{"line_number":318,"context_line":"  * This will no longer be an issue since SAML assertions are X509 signed."},{"line_number":319,"context_line":""}],"source_content_type":"text/x-rst","patch_set":20,"id":"baada198_80d86cf0","line":316,"updated":"2014-07-18 16:09:14.000000000","message":"I think this might be out of the spec\u0027s scope but it would be good to think of external processes to handle out-of-band cases like this, so that when deployers start using this feature there is some idea of how the out of band process is suppose to work.","commit_id":"132406aadebc317b417edc860bbb53f50210a57c"},{"author":{"_account_id":5046,"name":"Lance Bragstad","email":"lbragstad@redhat.com","username":"ldbragst"},"change_message_id":"b9a204ce45ccc2ea6b2677cd45a78da1bc8ddf2e","unresolved":false,"context_lines":[{"line_number":313,"context_line":""},{"line_number":314,"context_line":"* Does this increase the surface area of an attack if a cloud is compromised?"},{"line_number":315,"context_line":"  For example, say ACME has a partnership with BETA and DELTA as SPs. A"},{"line_number":316,"context_line":"  compromise of BETA is a Compromise of ACME and DELTA at the token level."},{"line_number":317,"context_line":""},{"line_number":318,"context_line":"  * This will no longer be an issue since SAML assertions are X509 signed."},{"line_number":319,"context_line":""}],"source_content_type":"text/x-rst","patch_set":20,"id":"baada198_833eb6b6","line":316,"in_reply_to":"baada198_80d86cf0","updated":"2014-07-18 16:15:15.000000000","message":"From a conversation I just had with Joe, we could carry this type of information in the README.md of the implementation, and I would be just fine with that.","commit_id":"132406aadebc317b417edc860bbb53f50210a57c"},{"author":{"_account_id":5046,"name":"Lance Bragstad","email":"lbragstad@redhat.com","username":"ldbragst"},"change_message_id":"7d5436d4f5a0d5efeef600cc6efac6c489b983cc","unresolved":false,"context_lines":[{"line_number":335,"context_line":"The following operations may impact performance:"},{"line_number":336,"context_line":""},{"line_number":337,"context_line":"* Since there could be as many service providers as regions, the catalog may"},{"line_number":338,"context_line":"  become larger. However this limitation exist today a catalog can have many"},{"line_number":339,"context_line":"  endpoints and also become pretty large with the endpoints that a user has"},{"line_number":340,"context_line":"  access to."},{"line_number":341,"context_line":""}],"source_content_type":"text/x-rst","patch_set":20,"id":"baada198_209c000e","line":338,"updated":"2014-07-18 16:09:14.000000000","message":"exists*","commit_id":"132406aadebc317b417edc860bbb53f50210a57c"},{"author":{"_account_id":11428,"name":"Ajaya Agrawal","email":"ajku.agr@gmail.com","username":"ajayaa"},"change_message_id":"e064c4b5c3fb24685b9347515c845d23958651ae","unresolved":false,"context_lines":[{"line_number":335,"context_line":"The following operations may impact performance:"},{"line_number":336,"context_line":""},{"line_number":337,"context_line":"* Since there could be as many service providers as regions, the catalog may"},{"line_number":338,"context_line":"  become larger. However this limitation exist today a catalog can have many"},{"line_number":339,"context_line":"  endpoints and also become pretty large with the endpoints that a user has"},{"line_number":340,"context_line":"  access to."},{"line_number":341,"context_line":""}],"source_content_type":"text/x-rst","patch_set":20,"id":"baada198_6c404360","line":338,"updated":"2014-07-29 06:18:52.000000000","message":"s/a catalog/as a catalog","commit_id":"132406aadebc317b417edc860bbb53f50210a57c"},{"author":{"_account_id":6482,"name":"Steve Martinelli","email":"s.martinelli@gmail.com","username":"stevemar"},"change_message_id":"fe03bc5bd8d42b26b538059e736a026fb83d4312","unresolved":false,"context_lines":[{"line_number":335,"context_line":"The following operations may impact performance:"},{"line_number":336,"context_line":""},{"line_number":337,"context_line":"* Since there could be as many service providers as regions, the catalog may"},{"line_number":338,"context_line":"  become larger. However this limitation exist today a catalog can have many"},{"line_number":339,"context_line":"  endpoints and also become pretty large with the endpoints that a user has"},{"line_number":340,"context_line":"  access to."},{"line_number":341,"context_line":""}],"source_content_type":"text/x-rst","patch_set":20,"id":"baada198_1270bc07","line":338,"in_reply_to":"baada198_6c404360","updated":"2014-07-29 07:19:03.000000000","message":"please submit a patch to fix the typos rather than comment on something that has been merged.","commit_id":"132406aadebc317b417edc860bbb53f50210a57c"},{"author":{"_account_id":9959,"name":"Craig A. Lee","email":"lee@aero.org","username":"craigalee"},"change_message_id":"406dd0e06592d52d1fd2aae0c931870f60f9913d","unresolved":false,"context_lines":[{"line_number":337,"context_line":"* Since there could be as many service providers as regions, the catalog may"},{"line_number":338,"context_line":"  become larger. However this limitation exist today a catalog can have many"},{"line_number":339,"context_line":"  endpoints and also become pretty large with the endpoints that a user has"},{"line_number":340,"context_line":"  access to."},{"line_number":341,"context_line":""},{"line_number":342,"context_line":"* More certificates to validate tokens against."},{"line_number":343,"context_line":""}],"source_content_type":"text/x-rst","patch_set":20,"id":"baada198_e4b31108","line":340,"updated":"2014-07-18 06:26:56.000000000","message":"I don\u0027t think \"region\" is the right word.  Why not simply say \"Since there could be many trusted service providers, the catalog may become ...\"","commit_id":"132406aadebc317b417edc860bbb53f50210a57c"},{"author":{"_account_id":6534,"name":"David Chadwick","email":"d.w.chadwick@truetrust.co.uk","username":"d-w-chadwick"},"change_message_id":"55c6c41faaf1ebbbae87b84863a3954d5c897be1","unresolved":false,"context_lines":[{"line_number":337,"context_line":"* Since there could be as many service providers as regions, the catalog may"},{"line_number":338,"context_line":"  become larger. However this limitation exist today a catalog can have many"},{"line_number":339,"context_line":"  endpoints and also become pretty large with the endpoints that a user has"},{"line_number":340,"context_line":"  access to."},{"line_number":341,"context_line":""},{"line_number":342,"context_line":"* More certificates to validate tokens against."},{"line_number":343,"context_line":""}],"source_content_type":"text/x-rst","patch_set":20,"id":"baada198_019b69c9","line":340,"in_reply_to":"baada198_e4b31108","updated":"2014-07-19 17:28:57.000000000","message":"I agree. Region is not correct as there can be many SPs per region, and one SP could cover several regions ie. there is a many to many mapping between regions and SPs.","commit_id":"132406aadebc317b417edc860bbb53f50210a57c"},{"author":{"_account_id":6534,"name":"David Chadwick","email":"d.w.chadwick@truetrust.co.uk","username":"d-w-chadwick"},"change_message_id":"07c0b9fcf2cc524721071cc6b1846872715fcb68","unresolved":false,"context_lines":[{"line_number":380,"context_line":""},{"line_number":381,"context_line":"* Define and implement a method of invalidating tokens across service"},{"line_number":382,"context_line":"  providers."},{"line_number":383,"context_line":""},{"line_number":384,"context_line":"Dependencies"},{"line_number":385,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":386,"context_line":""}],"source_content_type":"text/x-rst","patch_set":20,"id":"baada198_1b5c0d19","line":383,"updated":"2014-07-17 09:41:18.000000000","message":"Do you mean revoking tokens? If a token is invalid it will never be used. It if is valid, then later become invalid, it needs revoking.","commit_id":"132406aadebc317b417edc860bbb53f50210a57c"}]}
