)]}'
{"specs/keystone/queens/application-credentials.rst":[{"author":{"_account_id":5046,"name":"Lance Bragstad","email":"lbragstad@redhat.com","username":"ldbragst"},"change_message_id":"743d1a54233a43d26d60420d674147a97924ebad","unresolved":false,"context_lines":[{"line_number":72,"context_line":"credential, rolling the new credential out, then deleting the old credential"},{"line_number":73,"context_line":"for credential rotation with no downtime."},{"line_number":74,"context_line":""},{"line_number":75,"context_line":"* As a team of OpenStack Consumers, I want to be able to make Applications"},{"line_number":76,"context_line":"  that will not stop working when one of my Team Members leaves."},{"line_number":77,"context_line":""},{"line_number":78,"context_line":"As the use of Automation increases in the world, more and more teams have"},{"line_number":79,"context_line":"problems with automation that was tied to a specific Consumer\u0027s User"},{"line_number":80,"context_line":"credentials. The application credentials should be managed as Project level"},{"line_number":81,"context_line":"resources so that all Consumers who have Users with write-allowed roles on the"},{"line_number":82,"context_line":"Project can rotate or delete them as they see fit if membership in their Team"},{"line_number":83,"context_line":"changes."},{"line_number":84,"context_line":""},{"line_number":85,"context_line":"* As an OpenStack Deployer, I need to configure some OpenStack Services to be"},{"line_number":86,"context_line":"  able to make API calls to other OpenStack Services."}],"source_content_type":"text/x-rst","patch_set":1,"id":"ff82abbf_64dc9046","line":83,"range":{"start_line":75,"start_character":0,"end_line":83,"end_character":8},"updated":"2017-11-20 18:27:46.000000000","message":"This is going to have to be reworked since it goes against what we decided on at the PTG. Instead, we can have a statement that focuses on what the new proposal fixes (e.g. application credential won\u0027t prevent you application from breaking when a user leaves, but it does make your application more secure by incorporating role scope and removing user specific passwords from disk).\n\nIt also might be a good opportunity to explain how teams of people manage this problem. If they foresee a team change, then someone can create a new application credentials and do the rotation gracefully. That might be better noted in the Application Credential Management section.","commit_id":"1048e6450bfbc147a3570f79314e32215c46b845"},{"author":{"_account_id":8482,"name":"Colleen Murphy","email":"colleen@gazlene.net","username":"krinkle"},"change_message_id":"bdd5718acd7c475fd1296a9682035ed7e899d50a","unresolved":false,"context_lines":[{"line_number":72,"context_line":"credential, rolling the new credential out, then deleting the old credential"},{"line_number":73,"context_line":"for credential rotation with no downtime."},{"line_number":74,"context_line":""},{"line_number":75,"context_line":"* As a team of OpenStack Consumers, I want to be able to make Applications"},{"line_number":76,"context_line":"  that will not stop working when one of my Team Members leaves."},{"line_number":77,"context_line":""},{"line_number":78,"context_line":"As the use of Automation increases in the world, more and more teams have"},{"line_number":79,"context_line":"problems with automation that was tied to a specific Consumer\u0027s User"},{"line_number":80,"context_line":"credentials. The application credentials should be managed as Project level"},{"line_number":81,"context_line":"resources so that all Consumers who have Users with write-allowed roles on the"},{"line_number":82,"context_line":"Project can rotate or delete them as they see fit if membership in their Team"},{"line_number":83,"context_line":"changes."},{"line_number":84,"context_line":""},{"line_number":85,"context_line":"* As an OpenStack Deployer, I need to configure some OpenStack Services to be"},{"line_number":86,"context_line":"  able to make API calls to other OpenStack Services."}],"source_content_type":"text/x-rst","patch_set":1,"id":"ff82abbf_f7457416","line":83,"range":{"start_line":75,"start_character":0,"end_line":83,"end_character":8},"in_reply_to":"ff82abbf_64dc9046","updated":"2017-11-22 16:23:50.000000000","message":"Done","commit_id":"1048e6450bfbc147a3570f79314e32215c46b845"},{"author":{"_account_id":5046,"name":"Lance Bragstad","email":"lbragstad@redhat.com","username":"ldbragst"},"change_message_id":"eb454f702ab6840e6ec2a327c670cd4b638d9bfc","unresolved":false,"context_lines":[{"line_number":117,"context_line":"          intended to be, which is identification information intended for use"},{"line_number":118,"context_line":"          only by applications."},{"line_number":119,"context_line":""},{"line_number":120,"context_line":".. _`on the mailing list`: http://lists.openstack.org/pipermail/openstack-dev/2017-May/116596.html"},{"line_number":121,"context_line":""},{"line_number":122,"context_line":"Application Credentials will have the following characteristics:"},{"line_number":123,"context_line":""}],"source_content_type":"text/x-rst","patch_set":1,"id":"ff82abbf_42381c3c","line":120,"range":{"start_line":120,"start_character":0,"end_line":120,"end_character":98},"updated":"2017-11-22 16:32:07.000000000","message":"Do we no longer want to include this context because it is essentially summarized here?","commit_id":"1048e6450bfbc147a3570f79314e32215c46b845"},{"author":{"_account_id":8482,"name":"Colleen Murphy","email":"colleen@gazlene.net","username":"krinkle"},"change_message_id":"85ab50b78f0ea372cba1808656edae870a56653b","unresolved":false,"context_lines":[{"line_number":117,"context_line":"          intended to be, which is identification information intended for use"},{"line_number":118,"context_line":"          only by applications."},{"line_number":119,"context_line":""},{"line_number":120,"context_line":".. _`on the mailing list`: http://lists.openstack.org/pipermail/openstack-dev/2017-May/116596.html"},{"line_number":121,"context_line":""},{"line_number":122,"context_line":"Application Credentials will have the following characteristics:"},{"line_number":123,"context_line":""}],"source_content_type":"text/x-rst","patch_set":1,"id":"ff82abbf_ddc5f18f","line":120,"range":{"start_line":120,"start_character":0,"end_line":120,"end_character":98},"in_reply_to":"ff82abbf_42381c3c","updated":"2017-11-22 16:46:25.000000000","message":"It\u0027s not referenced by anything, I think an earlier draft of it must have referenced it and we deleted it.","commit_id":"1048e6450bfbc147a3570f79314e32215c46b845"},{"author":{"_account_id":5046,"name":"Lance Bragstad","email":"lbragstad@redhat.com","username":"ldbragst"},"change_message_id":"743d1a54233a43d26d60420d674147a97924ebad","unresolved":false,"context_lines":[{"line_number":130,"context_line":"* Secret exposed only once at creation time in the create API response."},{"line_number":131,"context_line":"* Limited ability to manipulate identity objects (see `Limitations Imposed`_)"},{"line_number":132,"context_line":"* Support expiration."},{"line_number":133,"context_line":"* Support deletion by any user with a write-allowed role in the project."},{"line_number":134,"context_line":"* Will be deleted when the associated User is deleted."},{"line_number":135,"context_line":""},{"line_number":136,"context_line":"Application Credentials will be treated as credentials and not authorization"}],"source_content_type":"text/x-rst","patch_set":1,"id":"ff82abbf_44914c52","line":133,"range":{"start_line":133,"start_character":0,"end_line":133,"end_character":72},"updated":"2017-11-20 18:27:46.000000000","message":"Did we talk about this at the PTG too? It seems to make sense to have it writable by everyone on the project, but I just want to make sure we\u0027re not glossing over this bit as a result of the new direction.","commit_id":"1048e6450bfbc147a3570f79314e32215c46b845"},{"author":{"_account_id":2903,"name":"Morgan Fainberg","email":"morgan.fainberg@gmail.com","username":"mdrnstm"},"change_message_id":"9b27076a54ada366db15ce01d1bea897d2ace6f1","unresolved":false,"context_lines":[{"line_number":130,"context_line":"* Secret exposed only once at creation time in the create API response."},{"line_number":131,"context_line":"* Limited ability to manipulate identity objects (see `Limitations Imposed`_)"},{"line_number":132,"context_line":"* Support expiration."},{"line_number":133,"context_line":"* Support deletion by any user with a write-allowed role in the project."},{"line_number":134,"context_line":"* Will be deleted when the associated User is deleted."},{"line_number":135,"context_line":""},{"line_number":136,"context_line":"Application Credentials will be treated as credentials and not authorization"}],"source_content_type":"text/x-rst","patch_set":1,"id":"ff82abbf_c41ebc6f","line":133,"range":{"start_line":133,"start_character":0,"end_line":133,"end_character":72},"in_reply_to":"ff82abbf_44914c52","updated":"2017-11-20 19:28:51.000000000","message":"At one point we talked about this. I want to say we nixed this idea as well (to start). There are potentially real concerns about creating an application credential for personal use that is then deleted by someone in the project. \n\nThat said, I can\u0027t concretely say this is a non-starter (nor would I block or-1 the proposal based upon this).","commit_id":"1048e6450bfbc147a3570f79314e32215c46b845"},{"author":{"_account_id":8482,"name":"Colleen Murphy","email":"colleen@gazlene.net","username":"krinkle"},"change_message_id":"bdd5718acd7c475fd1296a9682035ed7e899d50a","unresolved":false,"context_lines":[{"line_number":130,"context_line":"* Secret exposed only once at creation time in the create API response."},{"line_number":131,"context_line":"* Limited ability to manipulate identity objects (see `Limitations Imposed`_)"},{"line_number":132,"context_line":"* Support expiration."},{"line_number":133,"context_line":"* Support deletion by any user with a write-allowed role in the project."},{"line_number":134,"context_line":"* Will be deleted when the associated User is deleted."},{"line_number":135,"context_line":""},{"line_number":136,"context_line":"Application Credentials will be treated as credentials and not authorization"}],"source_content_type":"text/x-rst","patch_set":1,"id":"ff82abbf_37443c1b","line":133,"range":{"start_line":133,"start_character":0,"end_line":133,"end_character":72},"in_reply_to":"ff82abbf_c41ebc6f","updated":"2017-11-22 16:23:50.000000000","message":"I don\u0027t think we settled on this at either the PTG or the Forum. I\u0027m proposing that we keep it.\n\nIf we don\u0027t support general credential management by the whole project team, then it really stops making sense for this API to live under /projects and should be moved to /users.\n\nBut even if its lifetime is tied to the creating user, I think allowing general management by the whole team is essential so that proper rotation can occur on a regular basis and when a team member is preparing to leave. I don\u0027t think it is likely that someone will expect to create an application credential for personal use on a shared project, just like someone can\u0027t assume that a VM they create in a shared project will be left alone.","commit_id":"1048e6450bfbc147a3570f79314e32215c46b845"},{"author":{"_account_id":5046,"name":"Lance Bragstad","email":"lbragstad@redhat.com","username":"ldbragst"},"change_message_id":"743d1a54233a43d26d60420d674147a97924ebad","unresolved":false,"context_lines":[{"line_number":146,"context_line":"          described or implemented here, but is required to fully meet the Use"},{"line_number":147,"context_line":"          Case associated with pre-defined subset of User actions."},{"line_number":148,"context_line":""},{"line_number":149,"context_line":".. note:: In the future, it may be possible to create an Application Credential"},{"line_number":150,"context_line":"          that can persist past the lifecycle of the User. That functionality"},{"line_number":151,"context_line":"          is not described or implemented here, but is required to fully meet"},{"line_number":152,"context_line":"          the Use Case associated with automation not ceasing to work when"},{"line_number":153,"context_line":"          a human leaves a team."},{"line_number":154,"context_line":""},{"line_number":155,"context_line":"Application Credential Management"},{"line_number":156,"context_line":"---------------------------------"}],"source_content_type":"text/x-rst","patch_set":1,"id":"ff82abbf_a45ff8e3","line":153,"range":{"start_line":149,"start_character":0,"end_line":153,"end_character":32},"updated":"2017-11-20 18:27:46.000000000","message":"Ultimately, this seems consistent with what we talked about at both PTG and the Forum feedback session. I suppose we could take the opportunity to elaborate on it if we feel that documenting the path to the decision is important for historical context. Just in case people come out of the woodwork later asking why we implemented application credentials the way we did.\n\nMaybe instead of a note, we just make a new section that encapsulates \"future work\"?","commit_id":"1048e6450bfbc147a3570f79314e32215c46b845"},{"author":{"_account_id":2903,"name":"Morgan Fainberg","email":"morgan.fainberg@gmail.com","username":"mdrnstm"},"change_message_id":"9b27076a54ada366db15ce01d1bea897d2ace6f1","unresolved":false,"context_lines":[{"line_number":146,"context_line":"          described or implemented here, but is required to fully meet the Use"},{"line_number":147,"context_line":"          Case associated with pre-defined subset of User actions."},{"line_number":148,"context_line":""},{"line_number":149,"context_line":".. note:: In the future, it may be possible to create an Application Credential"},{"line_number":150,"context_line":"          that can persist past the lifecycle of the User. That functionality"},{"line_number":151,"context_line":"          is not described or implemented here, but is required to fully meet"},{"line_number":152,"context_line":"          the Use Case associated with automation not ceasing to work when"},{"line_number":153,"context_line":"          a human leaves a team."},{"line_number":154,"context_line":""},{"line_number":155,"context_line":"Application Credential Management"},{"line_number":156,"context_line":"---------------------------------"}],"source_content_type":"text/x-rst","patch_set":1,"id":"ff82abbf_bf03850d","line":153,"range":{"start_line":149,"start_character":0,"end_line":153,"end_character":32},"in_reply_to":"ff82abbf_a45ff8e3","updated":"2017-11-20 19:28:51.000000000","message":"+ Future work/Potential future directions.\n\nIT is not guaranteed we would add it. I would hedge on \"potential future direction\" and emphasize that this is not a guarantee.","commit_id":"1048e6450bfbc147a3570f79314e32215c46b845"},{"author":{"_account_id":8482,"name":"Colleen Murphy","email":"colleen@gazlene.net","username":"krinkle"},"change_message_id":"bdd5718acd7c475fd1296a9682035ed7e899d50a","unresolved":false,"context_lines":[{"line_number":146,"context_line":"          described or implemented here, but is required to fully meet the Use"},{"line_number":147,"context_line":"          Case associated with pre-defined subset of User actions."},{"line_number":148,"context_line":""},{"line_number":149,"context_line":".. note:: In the future, it may be possible to create an Application Credential"},{"line_number":150,"context_line":"          that can persist past the lifecycle of the User. That functionality"},{"line_number":151,"context_line":"          is not described or implemented here, but is required to fully meet"},{"line_number":152,"context_line":"          the Use Case associated with automation not ceasing to work when"},{"line_number":153,"context_line":"          a human leaves a team."},{"line_number":154,"context_line":""},{"line_number":155,"context_line":"Application Credential Management"},{"line_number":156,"context_line":"---------------------------------"}],"source_content_type":"text/x-rst","patch_set":1,"id":"ff82abbf_772ba481","line":153,"range":{"start_line":149,"start_character":0,"end_line":153,"end_character":32},"in_reply_to":"ff82abbf_a45ff8e3","updated":"2017-11-22 16:23:50.000000000","message":"Made a note about this in the security implications section.","commit_id":"1048e6450bfbc147a3570f79314e32215c46b845"},{"author":{"_account_id":8482,"name":"Colleen Murphy","email":"colleen@gazlene.net","username":"krinkle"},"change_message_id":"bdd5718acd7c475fd1296a9682035ed7e899d50a","unresolved":false,"context_lines":[{"line_number":146,"context_line":"          described or implemented here, but is required to fully meet the Use"},{"line_number":147,"context_line":"          Case associated with pre-defined subset of User actions."},{"line_number":148,"context_line":""},{"line_number":149,"context_line":".. note:: In the future, it may be possible to create an Application Credential"},{"line_number":150,"context_line":"          that can persist past the lifecycle of the User. That functionality"},{"line_number":151,"context_line":"          is not described or implemented here, but is required to fully meet"},{"line_number":152,"context_line":"          the Use Case associated with automation not ceasing to work when"},{"line_number":153,"context_line":"          a human leaves a team."},{"line_number":154,"context_line":""},{"line_number":155,"context_line":"Application Credential Management"},{"line_number":156,"context_line":"---------------------------------"}],"source_content_type":"text/x-rst","patch_set":1,"id":"ff82abbf_d712b058","line":153,"range":{"start_line":149,"start_character":0,"end_line":153,"end_character":32},"in_reply_to":"ff82abbf_bf03850d","updated":"2017-11-22 16:23:50.000000000","message":"My understanding is we\u0027re pretty solidly set on \"no\", not \"maybe in the future\". I\u0027m just going to remove it entirely.","commit_id":"1048e6450bfbc147a3570f79314e32215c46b845"},{"author":{"_account_id":5046,"name":"Lance Bragstad","email":"lbragstad@redhat.com","username":"ldbragst"},"change_message_id":"743d1a54233a43d26d60420d674147a97924ebad","unresolved":false,"context_lines":[{"line_number":382,"context_line":"the ability to further limit API use, the ability to start assigning"},{"line_number":383,"context_line":"Application Credentials per-service and performing expiration and rotation may"},{"line_number":384,"context_line":"be a desirable step forward that can be further enhanced with the addition of"},{"line_number":385,"context_line":"restricting an Application Credential\u0027s API Access."},{"line_number":386,"context_line":""},{"line_number":387,"context_line":".. _passlib: https://pypi.python.org/pypi/passlib"},{"line_number":388,"context_line":""}],"source_content_type":"text/x-rst","patch_set":1,"id":"ff82abbf_e4abc072","line":385,"updated":"2017-11-20 18:27:46.000000000","message":"++ Using service users this way also makes recovering compromised hosts easier and less painful.","commit_id":"1048e6450bfbc147a3570f79314e32215c46b845"},{"author":{"_account_id":8482,"name":"Colleen Murphy","email":"colleen@gazlene.net","username":"krinkle"},"change_message_id":"bdd5718acd7c475fd1296a9682035ed7e899d50a","unresolved":false,"context_lines":[{"line_number":395,"context_line":""},{"line_number":396,"context_line":"* POST /projects/{}/application_credentials"},{"line_number":397,"context_line":"* DELETE /projects/{}/application_credentials/{}"},{"line_number":398,"context_line":"* POST /users"},{"line_number":399,"context_line":"* PATCH /users/{}"},{"line_number":400,"context_line":"* DELETE /users/{}"},{"line_number":401,"context_line":"* POST /projects"},{"line_number":402,"context_line":"* PATCH /projects/{}"},{"line_number":403,"context_line":"* DELETE /projects/{}"},{"line_number":404,"context_line":"* PUT /projects/{}/users/{}/roles/{}"},{"line_number":405,"context_line":"* PUT /domains/{}/users/{}/roles/{}"},{"line_number":406,"context_line":"* PUT /projects/{}/groups/{}/roles/{}"},{"line_number":407,"context_line":"* PUT /domains/{}/groups/{}/roles/{}"},{"line_number":408,"context_line":""},{"line_number":409,"context_line":".. note:: It might be simpler and safer for now to just block a token"},{"line_number":410,"context_line":"          generated from an Application Credential from doing any action in"}],"source_content_type":"text/x-rst","patch_set":1,"id":"ff82abbf_bcb3534d","line":407,"range":{"start_line":398,"start_character":0,"end_line":407,"end_character":36},"updated":"2017-11-22 16:23:50.000000000","message":"I\u0027m thinking that explicitly excluding these is unnecessary. These are all admin actions, so only an app cred with an admin role could perform them. A user without an admin role won\u0027t be able to create an app cred that can do these, and a user with an admin role will be able to limit the cred\u0027s roles to just member. I\u0027m not sure we really need to single out keystone as being particularly dangerous.","commit_id":"1048e6450bfbc147a3570f79314e32215c46b845"},{"author":{"_account_id":5046,"name":"Lance Bragstad","email":"lbragstad@redhat.com","username":"ldbragst"},"change_message_id":"743d1a54233a43d26d60420d674147a97924ebad","unresolved":false,"context_lines":[{"line_number":406,"context_line":"* PUT /projects/{}/groups/{}/roles/{}"},{"line_number":407,"context_line":"* PUT /domains/{}/groups/{}/roles/{}"},{"line_number":408,"context_line":""},{"line_number":409,"context_line":".. note:: It might be simpler and safer for now to just block a token"},{"line_number":410,"context_line":"          generated from an Application Credential from doing any action in"},{"line_number":411,"context_line":"          Keystone altogether. This would check for an \"application_credential\""},{"line_number":412,"context_line":"          value in the \"methods\" key of a token object. This would be a"},{"line_number":413,"context_line":"          temporary measure until the followup API action exclusion support is"},{"line_number":414,"context_line":"          implemented."},{"line_number":415,"context_line":""},{"line_number":416,"context_line":"In the future, when the Consumer can expess additional REST API limitations"},{"line_number":417,"context_line":"at Application Credential creation time, the built-in identity blacklist should"}],"source_content_type":"text/x-rst","patch_set":1,"id":"ff82abbf_64b1f0e1","line":414,"range":{"start_line":409,"start_character":0,"end_line":414,"end_character":22},"updated":"2017-11-20 18:27:46.000000000","message":"With the exception of the heat case, where heat wants to be able to create an application credential using an application credential so that they can inject it into an instance.\n\nThoughts on calling that out specifically here?","commit_id":"1048e6450bfbc147a3570f79314e32215c46b845"},{"author":{"_account_id":8482,"name":"Colleen Murphy","email":"colleen@gazlene.net","username":"krinkle"},"change_message_id":"bdd5718acd7c475fd1296a9682035ed7e899d50a","unresolved":false,"context_lines":[{"line_number":406,"context_line":"* PUT /projects/{}/groups/{}/roles/{}"},{"line_number":407,"context_line":"* PUT /domains/{}/groups/{}/roles/{}"},{"line_number":408,"context_line":""},{"line_number":409,"context_line":".. note:: It might be simpler and safer for now to just block a token"},{"line_number":410,"context_line":"          generated from an Application Credential from doing any action in"},{"line_number":411,"context_line":"          Keystone altogether. This would check for an \"application_credential\""},{"line_number":412,"context_line":"          value in the \"methods\" key of a token object. This would be a"},{"line_number":413,"context_line":"          temporary measure until the followup API action exclusion support is"},{"line_number":414,"context_line":"          implemented."},{"line_number":415,"context_line":""},{"line_number":416,"context_line":"In the future, when the Consumer can expess additional REST API limitations"},{"line_number":417,"context_line":"at Application Credential creation time, the built-in identity blacklist should"}],"source_content_type":"text/x-rst","patch_set":1,"id":"ff82abbf_1c3b5feb","line":414,"range":{"start_line":409,"start_character":0,"end_line":414,"end_character":22},"in_reply_to":"ff82abbf_3f5c554a","updated":"2017-11-22 16:23:50.000000000","message":"Done","commit_id":"1048e6450bfbc147a3570f79314e32215c46b845"},{"author":{"_account_id":8482,"name":"Colleen Murphy","email":"colleen@gazlene.net","username":"krinkle"},"change_message_id":"bdd5718acd7c475fd1296a9682035ed7e899d50a","unresolved":false,"context_lines":[{"line_number":406,"context_line":"* PUT /projects/{}/groups/{}/roles/{}"},{"line_number":407,"context_line":"* PUT /domains/{}/groups/{}/roles/{}"},{"line_number":408,"context_line":""},{"line_number":409,"context_line":".. note:: It might be simpler and safer for now to just block a token"},{"line_number":410,"context_line":"          generated from an Application Credential from doing any action in"},{"line_number":411,"context_line":"          Keystone altogether. This would check for an \"application_credential\""},{"line_number":412,"context_line":"          value in the \"methods\" key of a token object. This would be a"},{"line_number":413,"context_line":"          temporary measure until the followup API action exclusion support is"},{"line_number":414,"context_line":"          implemented."},{"line_number":415,"context_line":""},{"line_number":416,"context_line":"In the future, when the Consumer can expess additional REST API limitations"},{"line_number":417,"context_line":"at Application Credential creation time, the built-in identity blacklist should"}],"source_content_type":"text/x-rst","patch_set":1,"id":"ff82abbf_fc1f9b6d","line":414,"range":{"start_line":409,"start_character":0,"end_line":414,"end_character":22},"in_reply_to":"ff82abbf_64b1f0e1","updated":"2017-11-22 16:23:50.000000000","message":"Done","commit_id":"1048e6450bfbc147a3570f79314e32215c46b845"},{"author":{"_account_id":2903,"name":"Morgan Fainberg","email":"morgan.fainberg@gmail.com","username":"mdrnstm"},"change_message_id":"9b27076a54ada366db15ce01d1bea897d2ace6f1","unresolved":false,"context_lines":[{"line_number":406,"context_line":"* PUT /projects/{}/groups/{}/roles/{}"},{"line_number":407,"context_line":"* PUT /domains/{}/groups/{}/roles/{}"},{"line_number":408,"context_line":""},{"line_number":409,"context_line":".. note:: It might be simpler and safer for now to just block a token"},{"line_number":410,"context_line":"          generated from an Application Credential from doing any action in"},{"line_number":411,"context_line":"          Keystone altogether. This would check for an \"application_credential\""},{"line_number":412,"context_line":"          value in the \"methods\" key of a token object. This would be a"},{"line_number":413,"context_line":"          temporary measure until the followup API action exclusion support is"},{"line_number":414,"context_line":"          implemented."},{"line_number":415,"context_line":""},{"line_number":416,"context_line":"In the future, when the Consumer can expess additional REST API limitations"},{"line_number":417,"context_line":"at Application Credential creation time, the built-in identity blacklist should"}],"source_content_type":"text/x-rst","patch_set":1,"id":"ff82abbf_3f5c554a","line":414,"range":{"start_line":409,"start_character":0,"end_line":414,"end_character":22},"in_reply_to":"ff82abbf_64b1f0e1","updated":"2017-11-20 19:28:51.000000000","message":"REmove the \"it might\" and provide guidance that we might have a simple flag for \"can work on keystone\" [if we\u0027re doing that]","commit_id":"1048e6450bfbc147a3570f79314e32215c46b845"},{"author":{"_account_id":5046,"name":"Lance Bragstad","email":"lbragstad@redhat.com","username":"ldbragst"},"change_message_id":"743d1a54233a43d26d60420d674147a97924ebad","unresolved":false,"context_lines":[{"line_number":441,"context_line":"insufficient for use by applications."},{"line_number":442,"context_line":""},{"line_number":443,"context_line":"`Enhance users`_ by adding new credential types and then allowing role"},{"line_number":444,"context_line":"assignments to be assigned to credential types instead of users. This doesn\u0027t"},{"line_number":445,"context_line":"solve the problem of applications needing to continue running after a User has"},{"line_number":446,"context_line":"been decommissioned. Additionally, regular Consumers frequently do not have"},{"line_number":447,"context_line":"permission to create Users, especially in places that use an identity backend"},{"line_number":448,"context_line":"like LDAP or AD."},{"line_number":449,"context_line":""}],"source_content_type":"text/x-rst","patch_set":1,"id":"ff82abbf_a4dcd818","line":446,"range":{"start_line":444,"start_character":65,"end_line":446,"end_character":20},"updated":"2017-11-20 18:27:46.000000000","message":"I don\u0027t think this is going to be applicable after the most recent discussions, since we\u0027re going to be removing a user\u0027s application credentials after a user is deleted. So this problem will still exist.","commit_id":"1048e6450bfbc147a3570f79314e32215c46b845"},{"author":{"_account_id":8482,"name":"Colleen Murphy","email":"colleen@gazlene.net","username":"krinkle"},"change_message_id":"bdd5718acd7c475fd1296a9682035ed7e899d50a","unresolved":false,"context_lines":[{"line_number":441,"context_line":"insufficient for use by applications."},{"line_number":442,"context_line":""},{"line_number":443,"context_line":"`Enhance users`_ by adding new credential types and then allowing role"},{"line_number":444,"context_line":"assignments to be assigned to credential types instead of users. This doesn\u0027t"},{"line_number":445,"context_line":"solve the problem of applications needing to continue running after a User has"},{"line_number":446,"context_line":"been decommissioned. Additionally, regular Consumers frequently do not have"},{"line_number":447,"context_line":"permission to create Users, especially in places that use an identity backend"},{"line_number":448,"context_line":"like LDAP or AD."},{"line_number":449,"context_line":""}],"source_content_type":"text/x-rst","patch_set":1,"id":"ff82abbf_7c4f0b92","line":446,"range":{"start_line":444,"start_character":65,"end_line":446,"end_character":20},"in_reply_to":"ff82abbf_a4dcd818","updated":"2017-11-22 16:23:50.000000000","message":"Done","commit_id":"1048e6450bfbc147a3570f79314e32215c46b845"},{"author":{"_account_id":5046,"name":"Lance Bragstad","email":"lbragstad@redhat.com","username":"ldbragst"},"change_message_id":"743d1a54233a43d26d60420d674147a97924ebad","unresolved":false,"context_lines":[{"line_number":451,"context_line":"adding OAuth on top of an existing Auth system is a deployer opt-in task that"},{"line_number":452,"context_line":"involves considerable deployer effort. If the goal is to add support for a"},{"line_number":453,"context_line":"concept that will always dependably exist, OAuth represents too high of a"},{"line_number":454,"context_line":"burden to be reasonable. Moreover, OAuth tokens have the same flaws as regular"},{"line_number":455,"context_line":"keystone tokens, namely that they are tied to a User, rather than a project,"},{"line_number":456,"context_line":"and that they are required to expire, rather than optionally expiring."},{"line_number":457,"context_line":""},{"line_number":458,"context_line":"`Enhance trusts`_ by detaching them from Users. Trusts still require role"},{"line_number":459,"context_line":"assignments on projects to be created by administrators. Adding the ability to"}],"source_content_type":"text/x-rst","patch_set":1,"id":"ff82abbf_44cdcc5b","line":456,"range":{"start_line":454,"start_character":25,"end_line":456,"end_character":70},"updated":"2017-11-20 18:27:46.000000000","message":"Same comment here. Since we\u0027re keeping the application credential scoped to the user, this might not make sense anymore.","commit_id":"1048e6450bfbc147a3570f79314e32215c46b845"},{"author":{"_account_id":2903,"name":"Morgan Fainberg","email":"morgan.fainberg@gmail.com","username":"mdrnstm"},"change_message_id":"9b27076a54ada366db15ce01d1bea897d2ace6f1","unresolved":false,"context_lines":[{"line_number":451,"context_line":"adding OAuth on top of an existing Auth system is a deployer opt-in task that"},{"line_number":452,"context_line":"involves considerable deployer effort. If the goal is to add support for a"},{"line_number":453,"context_line":"concept that will always dependably exist, OAuth represents too high of a"},{"line_number":454,"context_line":"burden to be reasonable. Moreover, OAuth tokens have the same flaws as regular"},{"line_number":455,"context_line":"keystone tokens, namely that they are tied to a User, rather than a project,"},{"line_number":456,"context_line":"and that they are required to expire, rather than optionally expiring."},{"line_number":457,"context_line":""},{"line_number":458,"context_line":"`Enhance trusts`_ by detaching them from Users. Trusts still require role"},{"line_number":459,"context_line":"assignments on projects to be created by administrators. Adding the ability to"}],"source_content_type":"text/x-rst","patch_set":1,"id":"ff82abbf_df068921","line":456,"range":{"start_line":454,"start_character":25,"end_line":456,"end_character":70},"in_reply_to":"ff82abbf_44cdcc5b","updated":"2017-11-20 19:28:51.000000000","message":"++","commit_id":"1048e6450bfbc147a3570f79314e32215c46b845"},{"author":{"_account_id":8482,"name":"Colleen Murphy","email":"colleen@gazlene.net","username":"krinkle"},"change_message_id":"bdd5718acd7c475fd1296a9682035ed7e899d50a","unresolved":false,"context_lines":[{"line_number":451,"context_line":"adding OAuth on top of an existing Auth system is a deployer opt-in task that"},{"line_number":452,"context_line":"involves considerable deployer effort. If the goal is to add support for a"},{"line_number":453,"context_line":"concept that will always dependably exist, OAuth represents too high of a"},{"line_number":454,"context_line":"burden to be reasonable. Moreover, OAuth tokens have the same flaws as regular"},{"line_number":455,"context_line":"keystone tokens, namely that they are tied to a User, rather than a project,"},{"line_number":456,"context_line":"and that they are required to expire, rather than optionally expiring."},{"line_number":457,"context_line":""},{"line_number":458,"context_line":"`Enhance trusts`_ by detaching them from Users. Trusts still require role"},{"line_number":459,"context_line":"assignments on projects to be created by administrators. Adding the ability to"}],"source_content_type":"text/x-rst","patch_set":1,"id":"ff82abbf_bc7b53bc","line":456,"range":{"start_line":454,"start_character":25,"end_line":456,"end_character":70},"in_reply_to":"ff82abbf_df068921","updated":"2017-11-22 16:23:50.000000000","message":"Done","commit_id":"1048e6450bfbc147a3570f79314e32215c46b845"},{"author":{"_account_id":5046,"name":"Lance Bragstad","email":"lbragstad@redhat.com","username":"ldbragst"},"change_message_id":"743d1a54233a43d26d60420d674147a97924ebad","unresolved":false,"context_lines":[{"line_number":500,"context_line":"* Application Credentials can be gracefully rotated out of use and deleted"},{"line_number":501,"context_line":"  periodically, allowing Consumers and Deployers a mechanism to prevent"},{"line_number":502,"context_line":"  compromised Users without requiring swapping credentials in short amounts of"},{"line_number":503,"context_line":"  time that might cause service interruption or downtime."},{"line_number":504,"context_line":""},{"line_number":505,"context_line":"There is an inherent risk with adding a new credential type and changing"},{"line_number":506,"context_line":"authentication details. One such risk would be the allowing of many credentials"}],"source_content_type":"text/x-rst","patch_set":1,"id":"ff82abbf_44f62c92","line":503,"updated":"2017-11-20 18:27:46.000000000","message":"I suppose we could elaborate on this a bit more and say that we aren\u0027t exposing application credentials as project-lived, since we\u0027re erring on the side of security (in favor of usability I guess).","commit_id":"1048e6450bfbc147a3570f79314e32215c46b845"},{"author":{"_account_id":8482,"name":"Colleen Murphy","email":"colleen@gazlene.net","username":"krinkle"},"change_message_id":"bdd5718acd7c475fd1296a9682035ed7e899d50a","unresolved":false,"context_lines":[{"line_number":500,"context_line":"* Application Credentials can be gracefully rotated out of use and deleted"},{"line_number":501,"context_line":"  periodically, allowing Consumers and Deployers a mechanism to prevent"},{"line_number":502,"context_line":"  compromised Users without requiring swapping credentials in short amounts of"},{"line_number":503,"context_line":"  time that might cause service interruption or downtime."},{"line_number":504,"context_line":""},{"line_number":505,"context_line":"There is an inherent risk with adding a new credential type and changing"},{"line_number":506,"context_line":"authentication details. One such risk would be the allowing of many credentials"}],"source_content_type":"text/x-rst","patch_set":1,"id":"ff82abbf_dc7657d9","line":503,"in_reply_to":"ff82abbf_44f62c92","updated":"2017-11-22 16:23:50.000000000","message":"Done","commit_id":"1048e6450bfbc147a3570f79314e32215c46b845"},{"author":{"_account_id":5046,"name":"Lance Bragstad","email":"lbragstad@redhat.com","username":"ldbragst"},"change_message_id":"743d1a54233a43d26d60420d674147a97924ebad","unresolved":false,"context_lines":[{"line_number":562,"context_line":""},{"line_number":563,"context_line":"Other contributors:"},{"line_number":564,"context_line":""},{"line_number":565,"context_line":"- Ron De Rose"},{"line_number":566,"context_line":"- Anthony Washington"},{"line_number":567,"context_line":"- TBD"},{"line_number":568,"context_line":""},{"line_number":569,"context_line":"Work Items"},{"line_number":570,"context_line":"----------"}],"source_content_type":"text/x-rst","patch_set":1,"id":"ff82abbf_84399442","line":567,"range":{"start_line":565,"start_character":0,"end_line":567,"end_character":5},"updated":"2017-11-20 18:27:46.000000000","message":"We might want to follow up with both just to make sure they are available to work on this.","commit_id":"1048e6450bfbc147a3570f79314e32215c46b845"},{"author":{"_account_id":5046,"name":"Lance Bragstad","email":"lbragstad@redhat.com","username":"ldbragst"},"change_message_id":"eb454f702ab6840e6ec2a327c670cd4b638d9bfc","unresolved":false,"context_lines":[{"line_number":160,"context_line":"Application Credentials. A User with a write-enabled role would be able to add"},{"line_number":161,"context_line":"and delete Application Credentials for that project."},{"line_number":162,"context_line":""},{"line_number":163,"context_line":"For example, adding an Application Credentials:"},{"line_number":164,"context_line":""},{"line_number":165,"context_line":"::"},{"line_number":166,"context_line":""}],"source_content_type":"text/x-rst","patch_set":2,"id":"ff82abbf_c243ccae","line":163,"range":{"start_line":163,"start_character":35,"end_line":163,"end_character":46},"updated":"2017-11-22 16:32:07.000000000","message":"nit: Credential* ?","commit_id":"4af331b2a90f3d5a844a778667a273d8e2495ad0"},{"author":{"_account_id":8482,"name":"Colleen Murphy","email":"colleen@gazlene.net","username":"krinkle"},"change_message_id":"acfcd96f1c63492d0c582a5d81eb9fe93407b5d9","unresolved":false,"context_lines":[{"line_number":160,"context_line":"Application Credentials. A User with a write-enabled role would be able to add"},{"line_number":161,"context_line":"and delete Application Credentials for that project."},{"line_number":162,"context_line":""},{"line_number":163,"context_line":"For example, adding an Application Credentials:"},{"line_number":164,"context_line":""},{"line_number":165,"context_line":"::"},{"line_number":166,"context_line":""}],"source_content_type":"text/x-rst","patch_set":2,"id":"ff82abbf_bdfd8db2","line":163,"range":{"start_line":163,"start_character":35,"end_line":163,"end_character":46},"in_reply_to":"ff82abbf_c243ccae","updated":"2017-11-22 16:49:52.000000000","message":"Done","commit_id":"4af331b2a90f3d5a844a778667a273d8e2495ad0"},{"author":{"_account_id":5046,"name":"Lance Bragstad","email":"lbragstad@redhat.com","username":"ldbragst"},"change_message_id":"eb454f702ab6840e6ec2a327c670cd4b638d9bfc","unresolved":false,"context_lines":[{"line_number":396,"context_line":"* DELETE /auth/tokens"},{"line_number":397,"context_line":""},{"line_number":398,"context_line":"It will do this by checking for an \"application_credential\" value in the"},{"line_number":399,"context_line":"\"methods\" key of a token object. This includes blocking the token API itself"},{"line_number":400,"context_line":"because we need to prevent an Application Credential from issuing itself a new"},{"line_number":401,"context_line":"token that has \"token\" as the \"method\" property and thereby working around the"},{"line_number":402,"context_line":"method check."},{"line_number":403,"context_line":""},{"line_number":404,"context_line":"This block can be disabled by adding an"},{"line_number":405,"context_line":"``\"allow_application_credential_creation\": true`` property to the application"}],"source_content_type":"text/x-rst","patch_set":2,"id":"ff82abbf_0251b462","line":402,"range":{"start_line":399,"start_character":33,"end_line":402,"end_character":13},"updated":"2017-11-22 16:32:07.000000000","message":"So application credentials are only good for validating tokens?","commit_id":"4af331b2a90f3d5a844a778667a273d8e2495ad0"},{"author":{"_account_id":8482,"name":"Colleen Murphy","email":"colleen@gazlene.net","username":"krinkle"},"change_message_id":"acfcd96f1c63492d0c582a5d81eb9fe93407b5d9","unresolved":false,"context_lines":[{"line_number":396,"context_line":"* DELETE /auth/tokens"},{"line_number":397,"context_line":""},{"line_number":398,"context_line":"It will do this by checking for an \"application_credential\" value in the"},{"line_number":399,"context_line":"\"methods\" key of a token object. This includes blocking the token API itself"},{"line_number":400,"context_line":"because we need to prevent an Application Credential from issuing itself a new"},{"line_number":401,"context_line":"token that has \"token\" as the \"method\" property and thereby working around the"},{"line_number":402,"context_line":"method check."},{"line_number":403,"context_line":""},{"line_number":404,"context_line":"This block can be disabled by adding an"},{"line_number":405,"context_line":"``\"allow_application_credential_creation\": true`` property to the application"}],"source_content_type":"text/x-rst","patch_set":2,"id":"ff82abbf_dde65117","line":402,"range":{"start_line":399,"start_character":33,"end_line":402,"end_character":13},"in_reply_to":"ff82abbf_0251b462","updated":"2017-11-22 16:49:52.000000000","message":"I was thinking that a token\u0027s methods list would get replaced, not appended, when a new token was issued. I think this is not the case and so this shouldn\u0027t be necessary.","commit_id":"4af331b2a90f3d5a844a778667a273d8e2495ad0"},{"author":{"_account_id":2903,"name":"Morgan Fainberg","email":"morgan.fainberg@gmail.com","username":"mdrnstm"},"change_message_id":"8603d584502c05e436172ba0278ba82af86a5868","unresolved":false,"context_lines":[{"line_number":137,"context_line":"* Secret exposed only once at creation time in the create API response."},{"line_number":138,"context_line":"* Limited ability to manipulate identity objects (see `Limitations Imposed`_)"},{"line_number":139,"context_line":"* Support expiration."},{"line_number":140,"context_line":"* Support deletion by any user with a write-allowed role in the project."},{"line_number":141,"context_line":"* Will be deleted when the associated User is deleted."},{"line_number":142,"context_line":""},{"line_number":143,"context_line":"Application Credentials will be treated as credentials and not authorization"}],"source_content_type":"text/x-rst","patch_set":3,"id":"ff82abbf_ef4a78aa","line":140,"range":{"start_line":140,"start_character":1,"end_line":140,"end_character":72},"updated":"2017-11-22 17:44:10.000000000","message":"I am still against this. The removal of app creds should happen automatically in these cases:\n\nUser is Deleted\nUser Loses roles/scope access on project that app cred relies on.\n\nA different user should not be allowed to delete the app cred just because they have write-access to the project.\n\nThis is the reason for my -1.","commit_id":"c9fbacf889a9a16eb8bdeff40bfa2fd65af5233c"},{"author":{"_account_id":5046,"name":"Lance Bragstad","email":"lbragstad@redhat.com","username":"ldbragst"},"change_message_id":"e5ae3eea212d1e78b4602e9590a59eba18bbccad","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":5,"id":"ff82abbf_cd80aac2","side":"PARENT","line":120,"range":{"start_line":120,"start_character":0,"end_line":120,"end_character":98},"updated":"2017-11-24 15:53:04.000000000","message":"We could slip this into the Reference sections so that the context is kept with the specification. But that can also be done in a follow up if needed.","commit_id":"e2c6a37428c07d07ce5aa797f5a373399c476293"},{"author":{"_account_id":8482,"name":"Colleen Murphy","email":"colleen@gazlene.net","username":"krinkle"},"change_message_id":"e9b3ecce46c5963f258a30c1980b2587f8d4ba13","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":5,"id":"ff82abbf_47978bed","side":"PARENT","line":120,"range":{"start_line":120,"start_character":0,"end_line":120,"end_character":98},"in_reply_to":"ff82abbf_cd80aac2","updated":"2017-11-26 14:57:16.000000000","message":"Done","commit_id":"e2c6a37428c07d07ce5aa797f5a373399c476293"},{"author":{"_account_id":5046,"name":"Lance Bragstad","email":"lbragstad@redhat.com","username":"ldbragst"},"change_message_id":"e5ae3eea212d1e78b4602e9590a59eba18bbccad","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":5,"id":"ff82abbf_0d4e9296","side":"PARENT","line":211,"range":{"start_line":211,"start_character":12,"end_line":211,"end_character":62},"updated":"2017-11-24 15:53:04.000000000","message":"This will still be referenced internally to keystone, just not exposed via the API, right?","commit_id":"e2c6a37428c07d07ce5aa797f5a373399c476293"},{"author":{"_account_id":8482,"name":"Colleen Murphy","email":"colleen@gazlene.net","username":"krinkle"},"change_message_id":"714412fdcda7d63ec778eb7157a37b9482ebefa7","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":5,"id":"ff82abbf_5edf62d5","side":"PARENT","line":211,"range":{"start_line":211,"start_character":12,"end_line":211,"end_character":62},"in_reply_to":"ff82abbf_0d4e9296","updated":"2017-11-24 18:48:15.000000000","message":"It will still have to be a property of the object but we retrieve it via /v3/users/{user_id}/... so I don\u0027t see a reason to include it on the JSON body.","commit_id":"e2c6a37428c07d07ce5aa797f5a373399c476293"},{"author":{"_account_id":8482,"name":"Colleen Murphy","email":"colleen@gazlene.net","username":"krinkle"},"change_message_id":"f950211b815d3cde6c0de002b0a1ba73f37c5564","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":5,"id":"ff82abbf_362c2998","side":"PARENT","line":348,"updated":"2017-11-23 09:09:09.000000000","message":"This just seemed out of place for the usage section, it\u0027s covered in the problem description.","commit_id":"e2c6a37428c07d07ce5aa797f5a373399c476293"},{"author":{"_account_id":5046,"name":"Lance Bragstad","email":"lbragstad@redhat.com","username":"ldbragst"},"change_message_id":"e5ae3eea212d1e78b4602e9590a59eba18bbccad","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":5,"id":"ff82abbf_88b05045","side":"PARENT","line":353,"range":{"start_line":350,"start_character":0,"end_line":353,"end_character":27},"updated":"2017-11-24 15:53:04.000000000","message":"Just to summarize, this is needed because a user\u0027s application credentials should be unique by name. They should also be only scoped to a specific project, which is determined by the token the user used to create the application credential. \n\nhttp://eavesdrop.openstack.org/irclogs/%23openstack-keystone/%23openstack-keystone.2017-11-24.log.html#t2017-11-24T15:06:41","commit_id":"e2c6a37428c07d07ce5aa797f5a373399c476293"},{"author":{"_account_id":8482,"name":"Colleen Murphy","email":"colleen@gazlene.net","username":"krinkle"},"change_message_id":"714412fdcda7d63ec778eb7157a37b9482ebefa7","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":5,"id":"ff82abbf_1ec55af1","side":"PARENT","line":353,"range":{"start_line":350,"start_character":0,"end_line":353,"end_character":27},"in_reply_to":"ff82abbf_88b05045","updated":"2017-11-24 18:48:15.000000000","message":"\u003e Just to summarize, this is needed because a user\u0027s application\n \u003e credentials should be unique by name.\n\nThis paragraph is describing the auth request example below which namespaces the credential by project. Credentials are no longer guaranteed to be unique by name either to a project or to a user, so namespacing it by a project no longer makes sense.","commit_id":"e2c6a37428c07d07ce5aa797f5a373399c476293"},{"author":{"_account_id":8482,"name":"Colleen Murphy","email":"colleen@gazlene.net","username":"krinkle"},"change_message_id":"f950211b815d3cde6c0de002b0a1ba73f37c5564","unresolved":false,"context_lines":[{"line_number":159,"context_line":"`name` can be useful as a short description when listing one\u0027s own Application"},{"line_number":160,"context_line":"Credentials, but there is no guarantee that it will be globally unique or"},{"line_number":161,"context_line":"unique within a project and so it cannot substitute the ID of the Application"},{"line_number":162,"context_line":"Credential in config files."},{"line_number":163,"context_line":""},{"line_number":164,"context_line":"`description` is a long description for storing information about the purpose"},{"line_number":165,"context_line":"of the Application Credential. It is mostly useful in reports or listings of"}],"source_content_type":"text/x-rst","patch_set":5,"id":"ff82abbf_131b3781","line":162,"updated":"2017-11-23 09:09:09.000000000","message":"Now that we\u0027re not talking about project-level things this is one of the usability implications. If a user can\u0027t list application credentials for a project then it is hardly fair to ask them to ensure they are giving theirs a unique name.","commit_id":"498b63e97cf8561bcd54a6deef7d2767c90e335b"},{"author":{"_account_id":5046,"name":"Lance Bragstad","email":"lbragstad@redhat.com","username":"ldbragst"},"change_message_id":"e5ae3eea212d1e78b4602e9590a59eba18bbccad","unresolved":false,"context_lines":[{"line_number":159,"context_line":"`name` can be useful as a short description when listing one\u0027s own Application"},{"line_number":160,"context_line":"Credentials, but there is no guarantee that it will be globally unique or"},{"line_number":161,"context_line":"unique within a project and so it cannot substitute the ID of the Application"},{"line_number":162,"context_line":"Credential in config files."},{"line_number":163,"context_line":""},{"line_number":164,"context_line":"`description` is a long description for storing information about the purpose"},{"line_number":165,"context_line":"of the Application Credential. It is mostly useful in reports or listings of"}],"source_content_type":"text/x-rst","patch_set":5,"id":"ff82abbf_ad8766b5","line":162,"in_reply_to":"ff82abbf_131b3781","updated":"2017-11-24 15:53:04.000000000","message":"Do we want to make sure the application credential name is unique given the user\u0027s application credentials? For example, should I be able to create two application credential for project \"Foo\" named \"backup\"?\n\nTechnically, the user would have all the information to ensure they aren\u0027t doing something like that.","commit_id":"498b63e97cf8561bcd54a6deef7d2767c90e335b"},{"author":{"_account_id":8482,"name":"Colleen Murphy","email":"colleen@gazlene.net","username":"krinkle"},"change_message_id":"4e6ea2ca16faca799f14e8e330414741bda81f8c","unresolved":false,"context_lines":[{"line_number":159,"context_line":"`name` can be useful as a short description when listing one\u0027s own Application"},{"line_number":160,"context_line":"Credentials, but there is no guarantee that it will be globally unique or"},{"line_number":161,"context_line":"unique within a project and so it cannot substitute the ID of the Application"},{"line_number":162,"context_line":"Credential in config files."},{"line_number":163,"context_line":""},{"line_number":164,"context_line":"`description` is a long description for storing information about the purpose"},{"line_number":165,"context_line":"of the Application Credential. It is mostly useful in reports or listings of"}],"source_content_type":"text/x-rst","patch_set":5,"id":"ff82abbf_070c2392","line":162,"in_reply_to":"ff82abbf_3e461ec2","updated":"2017-11-26 14:20:14.000000000","message":"This will end up causing a lot of hardship on deployment tools, maybe specifying unique credentials with username + credential name is the way to go","commit_id":"498b63e97cf8561bcd54a6deef7d2767c90e335b"},{"author":{"_account_id":8482,"name":"Colleen Murphy","email":"colleen@gazlene.net","username":"krinkle"},"change_message_id":"714412fdcda7d63ec778eb7157a37b9482ebefa7","unresolved":false,"context_lines":[{"line_number":159,"context_line":"`name` can be useful as a short description when listing one\u0027s own Application"},{"line_number":160,"context_line":"Credentials, but there is no guarantee that it will be globally unique or"},{"line_number":161,"context_line":"unique within a project and so it cannot substitute the ID of the Application"},{"line_number":162,"context_line":"Credential in config files."},{"line_number":163,"context_line":""},{"line_number":164,"context_line":"`description` is a long description for storing information about the purpose"},{"line_number":165,"context_line":"of the Application Credential. It is mostly useful in reports or listings of"}],"source_content_type":"text/x-rst","patch_set":5,"id":"ff82abbf_3e461ec2","line":162,"in_reply_to":"ff82abbf_ad8766b5","updated":"2017-11-24 18:48:15.000000000","message":"They would, but how would that be useful? They will still have to use the ID in config files because that\u0027s the only way to uniquely identify it globally. The only other option would be to require a username + credential name in order to identify it.","commit_id":"498b63e97cf8561bcd54a6deef7d2767c90e335b"},{"author":{"_account_id":5046,"name":"Lance Bragstad","email":"lbragstad@redhat.com","username":"ldbragst"},"change_message_id":"e5ae3eea212d1e78b4602e9590a59eba18bbccad","unresolved":false,"context_lines":[{"line_number":171,"context_line":"is not included."},{"line_number":172,"context_line":""},{"line_number":173,"context_line":"`roles` is an optional list of role names that is a subset of the roles"},{"line_number":174,"context_line":"the Creating User has on the Project to which they are scoped at creation time."},{"line_number":175,"context_line":"Roles that the Creating User does not have on the Project are an error."},{"line_number":176,"context_line":""},{"line_number":177,"context_line":"In the initial implementation, the Application Credential will assume the roles"},{"line_number":178,"context_line":"of the Creating User or the given subset and we will not implement"}],"source_content_type":"text/x-rst","patch_set":5,"id":"ff82abbf_4da9fa21","line":175,"range":{"start_line":174,"start_character":0,"end_line":175,"end_character":71},"updated":"2017-11-24 15:53:04.000000000","message":"What about when a user is removed from a project? Is keystone going to automatically update the application credential to remove those roles from that user\u0027s application credentials? Or is keystone going to invalidate the application credential? Or is keystone going to wait until the application credential attempts to do something with a token to validate the role assignments?\n\nIMO, I don\u0027t see a problem with automatically removing the role from all applicable application credentials owned by a user because someone else on the team should have assumed ownership of the application\u0027s the leaving user owns.","commit_id":"498b63e97cf8561bcd54a6deef7d2767c90e335b"},{"author":{"_account_id":5046,"name":"Lance Bragstad","email":"lbragstad@redhat.com","username":"ldbragst"},"change_message_id":"e5ae3eea212d1e78b4602e9590a59eba18bbccad","unresolved":false,"context_lines":[{"line_number":276,"context_line":"          a different error message. More thought and feedback on this are"},{"line_number":277,"context_line":"          needed, but are not essential for the first round of work."},{"line_number":278,"context_line":""},{"line_number":279,"context_line":"When the Creating User for an Application Credential is deleted, or if their"},{"line_number":280,"context_line":"roles on the Project to which the Application Credential is scoped are"},{"line_number":281,"context_line":"unassigned, that Application Credential is also deleted."},{"line_number":282,"context_line":""},{"line_number":283,"context_line":"Aside from deletion, Application Credentials are immutable and may not be"},{"line_number":284,"context_line":"modified."}],"source_content_type":"text/x-rst","patch_set":5,"id":"ff82abbf_c86df8cc","line":281,"range":{"start_line":279,"start_character":65,"end_line":281,"end_character":56},"updated":"2017-11-24 15:53:04.000000000","message":"I suppose if we make the application credential immutable, this is the only sensible action.\n\nFor example, if I have roles \u0027foo\u0027 and \u0027bar\u0027 on project \u0027Baz\u0027, I can create an application credential with both of those roles. Then if the \u0027foo\u0027 role is removed, should the application credential be updated (from keystone) to prune out the \u0027foo\u0027 role, or completely invalidated?\n\nThe more I think about it the more I learn towards the latter.","commit_id":"498b63e97cf8561bcd54a6deef7d2767c90e335b"},{"author":{"_account_id":5046,"name":"Lance Bragstad","email":"lbragstad@redhat.com","username":"ldbragst"},"change_message_id":"7d2e4a8a75ec38aea53f55381dfab3851d0b703e","unresolved":false,"context_lines":[{"line_number":276,"context_line":"          a different error message. More thought and feedback on this are"},{"line_number":277,"context_line":"          needed, but are not essential for the first round of work."},{"line_number":278,"context_line":""},{"line_number":279,"context_line":"When the Creating User for an Application Credential is deleted, or if their"},{"line_number":280,"context_line":"roles on the Project to which the Application Credential is scoped are"},{"line_number":281,"context_line":"unassigned, that Application Credential is also deleted."},{"line_number":282,"context_line":""},{"line_number":283,"context_line":"Aside from deletion, Application Credentials are immutable and may not be"},{"line_number":284,"context_line":"modified."}],"source_content_type":"text/x-rst","patch_set":5,"id":"ff82abbf_ffa89120","line":281,"range":{"start_line":279,"start_character":65,"end_line":281,"end_character":56},"in_reply_to":"ff82abbf_9e02ca3c","updated":"2017-11-27 20:35:54.000000000","message":"++ that makes sense","commit_id":"498b63e97cf8561bcd54a6deef7d2767c90e335b"},{"author":{"_account_id":8482,"name":"Colleen Murphy","email":"colleen@gazlene.net","username":"krinkle"},"change_message_id":"714412fdcda7d63ec778eb7157a37b9482ebefa7","unresolved":false,"context_lines":[{"line_number":276,"context_line":"          a different error message. More thought and feedback on this are"},{"line_number":277,"context_line":"          needed, but are not essential for the first round of work."},{"line_number":278,"context_line":""},{"line_number":279,"context_line":"When the Creating User for an Application Credential is deleted, or if their"},{"line_number":280,"context_line":"roles on the Project to which the Application Credential is scoped are"},{"line_number":281,"context_line":"unassigned, that Application Credential is also deleted."},{"line_number":282,"context_line":""},{"line_number":283,"context_line":"Aside from deletion, Application Credentials are immutable and may not be"},{"line_number":284,"context_line":"modified."}],"source_content_type":"text/x-rst","patch_set":5,"id":"ff82abbf_9e02ca3c","line":281,"range":{"start_line":279,"start_character":65,"end_line":281,"end_character":56},"in_reply_to":"ff82abbf_c86df8cc","updated":"2017-11-24 18:48:15.000000000","message":"If we keep the requirement that application credentials are immutable then invalidating it in this case is the only option.","commit_id":"498b63e97cf8561bcd54a6deef7d2767c90e335b"},{"author":{"_account_id":5046,"name":"Lance Bragstad","email":"lbragstad@redhat.com","username":"ldbragst"},"change_message_id":"e5ae3eea212d1e78b4602e9590a59eba18bbccad","unresolved":false,"context_lines":[{"line_number":339,"context_line":"* POST /v3/users/{}/application_credentials"},{"line_number":340,"context_line":"* DELETE /v3/users/{}/application_credentials/{}"},{"line_number":341,"context_line":""},{"line_number":342,"context_line":"It will do this by checking for an \"application_credential\" value in the"},{"line_number":343,"context_line":"\"methods\" key of a token object."},{"line_number":344,"context_line":""},{"line_number":345,"context_line":"This block can be disabled by adding an"},{"line_number":346,"context_line":"``\"allow_application_credential_creation\": true`` property to the application"}],"source_content_type":"text/x-rst","patch_set":5,"id":"ff82abbf_c87bb878","line":343,"range":{"start_line":342,"start_character":0,"end_line":343,"end_character":32},"updated":"2017-11-24 15:53:04.000000000","message":"Yeah - this is a good example of a \"scope\" check that we\u0027re maintaining in code.","commit_id":"498b63e97cf8561bcd54a6deef7d2767c90e335b"},{"author":{"_account_id":8482,"name":"Colleen Murphy","email":"colleen@gazlene.net","username":"krinkle"},"change_message_id":"f950211b815d3cde6c0de002b0a1ba73f37c5564","unresolved":false,"context_lines":[{"line_number":342,"context_line":"It will do this by checking for an \"application_credential\" value in the"},{"line_number":343,"context_line":"\"methods\" key of a token object."},{"line_number":344,"context_line":""},{"line_number":345,"context_line":"This block can be disabled by adding an"},{"line_number":346,"context_line":"``\"allow_application_credential_creation\": true`` property to the application"},{"line_number":347,"context_line":"credential at creation. This is to support a use case specific to Heat, where"},{"line_number":348,"context_line":"the Heat user\u0027s application credential should be allowed to create new"},{"line_number":349,"context_line":"application credentials to be injected into an instance."},{"line_number":350,"context_line":""},{"line_number":351,"context_line":"In the future, more fine-grained API Access List Controls will remove the need"},{"line_number":352,"context_line":"for such a block and the workaround for the block."}],"source_content_type":"text/x-rst","patch_set":5,"id":"ff82abbf_13649721","line":349,"range":{"start_line":345,"start_character":0,"end_line":349,"end_character":55},"updated":"2017-11-23 09:09:09.000000000","message":"I feel like we hand-waved over this at the PTG and just said \"we\u0027ll fix it in policy\", but I\u0027m not sure how this would work in practice since we\u0027re not really dealing with roles here. Suggestions welcome.","commit_id":"498b63e97cf8561bcd54a6deef7d2767c90e335b"},{"author":{"_account_id":8482,"name":"Colleen Murphy","email":"colleen@gazlene.net","username":"krinkle"},"change_message_id":"714412fdcda7d63ec778eb7157a37b9482ebefa7","unresolved":false,"context_lines":[{"line_number":342,"context_line":"It will do this by checking for an \"application_credential\" value in the"},{"line_number":343,"context_line":"\"methods\" key of a token object."},{"line_number":344,"context_line":""},{"line_number":345,"context_line":"This block can be disabled by adding an"},{"line_number":346,"context_line":"``\"allow_application_credential_creation\": true`` property to the application"},{"line_number":347,"context_line":"credential at creation. This is to support a use case specific to Heat, where"},{"line_number":348,"context_line":"the Heat user\u0027s application credential should be allowed to create new"},{"line_number":349,"context_line":"application credentials to be injected into an instance."},{"line_number":350,"context_line":""},{"line_number":351,"context_line":"In the future, more fine-grained API Access List Controls will remove the need"},{"line_number":352,"context_line":"for such a block and the workaround for the block."}],"source_content_type":"text/x-rst","patch_set":5,"id":"ff82abbf_5ea68255","line":349,"range":{"start_line":345,"start_character":0,"end_line":349,"end_character":55},"in_reply_to":"ff82abbf_08ebe012","updated":"2017-11-24 18:48:15.000000000","message":"Does it need to be specific to heat? Is there harm in allowing any user to say \"Yes I accept the risks, just let me do this\"?","commit_id":"498b63e97cf8561bcd54a6deef7d2767c90e335b"},{"author":{"_account_id":5046,"name":"Lance Bragstad","email":"lbragstad@redhat.com","username":"ldbragst"},"change_message_id":"e5ae3eea212d1e78b4602e9590a59eba18bbccad","unresolved":false,"context_lines":[{"line_number":342,"context_line":"It will do this by checking for an \"application_credential\" value in the"},{"line_number":343,"context_line":"\"methods\" key of a token object."},{"line_number":344,"context_line":""},{"line_number":345,"context_line":"This block can be disabled by adding an"},{"line_number":346,"context_line":"``\"allow_application_credential_creation\": true`` property to the application"},{"line_number":347,"context_line":"credential at creation. This is to support a use case specific to Heat, where"},{"line_number":348,"context_line":"the Heat user\u0027s application credential should be allowed to create new"},{"line_number":349,"context_line":"application credentials to be injected into an instance."},{"line_number":350,"context_line":""},{"line_number":351,"context_line":"In the future, more fine-grained API Access List Controls will remove the need"},{"line_number":352,"context_line":"for such a block and the workaround for the block."}],"source_content_type":"text/x-rst","patch_set":5,"id":"ff82abbf_08ebe012","line":349,"range":{"start_line":345,"start_character":0,"end_line":349,"end_character":55},"in_reply_to":"ff82abbf_13649721","updated":"2017-11-24 15:53:04.000000000","message":"Yeah - there has something something about how Heat creates the application credential or how Heat uses the application credentials that triggers this condition. But it has to be specific to Heat, or services like it, to not be abused.","commit_id":"498b63e97cf8561bcd54a6deef7d2767c90e335b"},{"author":{"_account_id":5046,"name":"Lance Bragstad","email":"lbragstad@redhat.com","username":"ldbragst"},"change_message_id":"7d2e4a8a75ec38aea53f55381dfab3851d0b703e","unresolved":false,"context_lines":[{"line_number":342,"context_line":"It will do this by checking for an \"application_credential\" value in the"},{"line_number":343,"context_line":"\"methods\" key of a token object."},{"line_number":344,"context_line":""},{"line_number":345,"context_line":"This block can be disabled by adding an"},{"line_number":346,"context_line":"``\"allow_application_credential_creation\": true`` property to the application"},{"line_number":347,"context_line":"credential at creation. This is to support a use case specific to Heat, where"},{"line_number":348,"context_line":"the Heat user\u0027s application credential should be allowed to create new"},{"line_number":349,"context_line":"application credentials to be injected into an instance."},{"line_number":350,"context_line":""},{"line_number":351,"context_line":"In the future, more fine-grained API Access List Controls will remove the need"},{"line_number":352,"context_line":"for such a block and the workaround for the block."}],"source_content_type":"text/x-rst","patch_set":5,"id":"ff82abbf_ff7df1b1","line":349,"range":{"start_line":345,"start_character":0,"end_line":349,"end_character":55},"in_reply_to":"ff82abbf_5ea68255","updated":"2017-11-27 20:35:54.000000000","message":"I thought I remember this applying to other services and not just heat (e.g. magnum?).","commit_id":"498b63e97cf8561bcd54a6deef7d2767c90e335b"},{"author":{"_account_id":5046,"name":"Lance Bragstad","email":"lbragstad@redhat.com","username":"ldbragst"},"change_message_id":"e5ae3eea212d1e78b4602e9590a59eba18bbccad","unresolved":false,"context_lines":[{"line_number":529,"context_line":"Documentation Impact"},{"line_number":530,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":531,"context_line":""},{"line_number":532,"context_line":"The in-tree installation guide should be updated to account for Application"},{"line_number":533,"context_line":"Credentials and Service Users. The user guides should also be updated to"},{"line_number":534,"context_line":"reflect the ability for Users to use Application Credentials for application"},{"line_number":535,"context_line":"authentication."},{"line_number":536,"context_line":""}],"source_content_type":"text/x-rst","patch_set":5,"id":"ff82abbf_a8dbd479","line":533,"range":{"start_line":532,"start_character":0,"end_line":533,"end_character":30},"updated":"2017-11-24 15:53:04.000000000","message":"Yes please!","commit_id":"498b63e97cf8561bcd54a6deef7d2767c90e335b"},{"author":{"_account_id":8482,"name":"Colleen Murphy","email":"colleen@gazlene.net","username":"krinkle"},"change_message_id":"21b48b63f23e61ad4f353349504639b88337e32c","unresolved":false,"context_lines":[{"line_number":143,"context_line":""},{"line_number":144,"context_line":"::"},{"line_number":145,"context_line":""},{"line_number":146,"context_line":"    POST /v3/users/{user_id}/application_credentials"},{"line_number":147,"context_line":""},{"line_number":148,"context_line":".. code-block:: json"},{"line_number":149,"context_line":""}],"source_content_type":"text/x-rst","patch_set":6,"id":"ff82abbf_7657c6cb","line":146,"updated":"2017-11-27 23:24:41.000000000","message":"Why don\u0027t we leverage our existing credentials API, make a new credential type? https://developer.openstack.org/api-ref/identity/v3/index.html#credentials","commit_id":"bb72c4899bd3d4f33f9ae803726ce615133ec58a"},{"author":{"_account_id":5046,"name":"Lance Bragstad","email":"lbragstad@redhat.com","username":"ldbragst"},"change_message_id":"a8e6c47c9026a04329d40169c37b28e05bb405e9","unresolved":false,"context_lines":[{"line_number":369,"context_line":"It will do this by checking for an \"application_credential\" value in the"},{"line_number":370,"context_line":"\"methods\" key of a token object."},{"line_number":371,"context_line":""},{"line_number":372,"context_line":"This block can be disabled by adding an"},{"line_number":373,"context_line":"``\"allow_application_credential_creation\": true`` property to the application"},{"line_number":374,"context_line":"credential at creation. This is to support a use case specific to Heat, where"},{"line_number":375,"context_line":"the Heat user\u0027s application credential should be allowed to create new"},{"line_number":376,"context_line":"application credentials to be injected into an instance."},{"line_number":377,"context_line":""}],"source_content_type":"text/x-rst","patch_set":6,"id":"ff82abbf_c285b05b","line":374,"range":{"start_line":372,"start_character":0,"end_line":374,"end_character":23},"updated":"2017-11-27 20:44:17.000000000","message":"Can this be done by anyone when they create their application credential?","commit_id":"bb72c4899bd3d4f33f9ae803726ce615133ec58a"},{"author":{"_account_id":8482,"name":"Colleen Murphy","email":"colleen@gazlene.net","username":"krinkle"},"change_message_id":"97e0876a63d59a7bb539cccbda785f761df1be05","unresolved":false,"context_lines":[{"line_number":369,"context_line":"It will do this by checking for an \"application_credential\" value in the"},{"line_number":370,"context_line":"\"methods\" key of a token object."},{"line_number":371,"context_line":""},{"line_number":372,"context_line":"This block can be disabled by adding an"},{"line_number":373,"context_line":"``\"allow_application_credential_creation\": true`` property to the application"},{"line_number":374,"context_line":"credential at creation. This is to support a use case specific to Heat, where"},{"line_number":375,"context_line":"the Heat user\u0027s application credential should be allowed to create new"},{"line_number":376,"context_line":"application credentials to be injected into an instance."},{"line_number":377,"context_line":""}],"source_content_type":"text/x-rst","patch_set":6,"id":"ff82abbf_b6d30e60","line":374,"range":{"start_line":372,"start_character":0,"end_line":374,"end_character":23},"in_reply_to":"ff82abbf_2b755764","updated":"2017-11-27 23:20:15.000000000","message":"Summing up what we talked about on IRC - this could be implemented by having two actions, say POST /v3/users/{}/application_credentials and POST /v3/users/{}/application_credentials_that_can_create_application_credentials (or something saner than that), so that we could apply normal policies to the different routes. Creating an application_credential_that_can_create_application_credentials would result in the same object with a special flag that can be handled specially internally. But it sounds like Morgan is also okay with the \"I accept the risks, just do it\" way.\n\nEither way, the block list will have to include not just all the application_credentials endpoints but also trusts.","commit_id":"bb72c4899bd3d4f33f9ae803726ce615133ec58a"},{"author":{"_account_id":2903,"name":"Morgan Fainberg","email":"morgan.fainberg@gmail.com","username":"mdrnstm"},"change_message_id":"a8a922348e5279c526f35e6577524f07b140eafc","unresolved":false,"context_lines":[{"line_number":369,"context_line":"It will do this by checking for an \"application_credential\" value in the"},{"line_number":370,"context_line":"\"methods\" key of a token object."},{"line_number":371,"context_line":""},{"line_number":372,"context_line":"This block can be disabled by adding an"},{"line_number":373,"context_line":"``\"allow_application_credential_creation\": true`` property to the application"},{"line_number":374,"context_line":"credential at creation. This is to support a use case specific to Heat, where"},{"line_number":375,"context_line":"the Heat user\u0027s application credential should be allowed to create new"},{"line_number":376,"context_line":"application credentials to be injected into an instance."},{"line_number":377,"context_line":""}],"source_content_type":"text/x-rst","patch_set":6,"id":"ff82abbf_2b755764","line":374,"range":{"start_line":372,"start_character":0,"end_line":374,"end_character":23},"in_reply_to":"ff82abbf_8257a8ca","updated":"2017-11-27 22:42:53.000000000","message":"How would we limit it? Limiting to a specific USER_ID is a pain to configure/maintain.\n\nTypically I don\u0027t advocate something like this but.....\n\nLets make generic application credentials that can apply to anything but identity this API and another path for identity-specific app-creds? The underlying code can be identical except for an attribute allowing access to Identity. This allows for proper (consistent) RBAC locking of access to services such as magnum without blocking access for normal users to do the normal thing.\n\nI do mean that the APIs would be identical except that the \"only acts on identity\" flag would be added to the second API path. [Yes, an Identity-specific app-cred should not work on anything else if we go down this path]..","commit_id":"bb72c4899bd3d4f33f9ae803726ce615133ec58a"},{"author":{"_account_id":2903,"name":"Morgan Fainberg","email":"morgan.fainberg@gmail.com","username":"mdrnstm"},"change_message_id":"de543a18b398ad4cadab292f41e34b5c1db3cf8c","unresolved":false,"context_lines":[{"line_number":369,"context_line":"It will do this by checking for an \"application_credential\" value in the"},{"line_number":370,"context_line":"\"methods\" key of a token object."},{"line_number":371,"context_line":""},{"line_number":372,"context_line":"This block can be disabled by adding an"},{"line_number":373,"context_line":"``\"allow_application_credential_creation\": true`` property to the application"},{"line_number":374,"context_line":"credential at creation. This is to support a use case specific to Heat, where"},{"line_number":375,"context_line":"the Heat user\u0027s application credential should be allowed to create new"},{"line_number":376,"context_line":"application credentials to be injected into an instance."},{"line_number":377,"context_line":""}],"source_content_type":"text/x-rst","patch_set":6,"id":"ff82abbf_36e85ee0","line":374,"range":{"start_line":372,"start_character":0,"end_line":374,"end_character":23},"in_reply_to":"ff82abbf_b6d30e60","updated":"2017-11-27 23:27:00.000000000","message":"Colleen summarized it perfectly.\n\nThanks! You beat me to adding to the note here ;)","commit_id":"bb72c4899bd3d4f33f9ae803726ce615133ec58a"},{"author":{"_account_id":8482,"name":"Colleen Murphy","email":"colleen@gazlene.net","username":"krinkle"},"change_message_id":"ea9154781628ca2bda2889b164a3c394dd1b9b59","unresolved":false,"context_lines":[{"line_number":369,"context_line":"It will do this by checking for an \"application_credential\" value in the"},{"line_number":370,"context_line":"\"methods\" key of a token object."},{"line_number":371,"context_line":""},{"line_number":372,"context_line":"This block can be disabled by adding an"},{"line_number":373,"context_line":"``\"allow_application_credential_creation\": true`` property to the application"},{"line_number":374,"context_line":"credential at creation. This is to support a use case specific to Heat, where"},{"line_number":375,"context_line":"the Heat user\u0027s application credential should be allowed to create new"},{"line_number":376,"context_line":"application credentials to be injected into an instance."},{"line_number":377,"context_line":""}],"source_content_type":"text/x-rst","patch_set":6,"id":"ff82abbf_8257a8ca","line":374,"range":{"start_line":372,"start_character":0,"end_line":374,"end_character":23},"in_reply_to":"ff82abbf_c285b05b","updated":"2017-11-27 20:50:23.000000000","message":"That\u0027s my open question. Is there harm in allowing someone to say \"yes I know the risks, just let me do this\"? Should this somehow be limited to particular services e.g. Heat and Magnum? If that\u0027s the case, how do we accomplish this - make setting this property an admin action? Or do we say application credentials with user_id \u003d\u003d {heat user} to POST /v3/users/{}/application_credentials ? Or make use of the service token somehow?","commit_id":"bb72c4899bd3d4f33f9ae803726ce615133ec58a"},{"author":{"_account_id":8482,"name":"Colleen Murphy","email":"colleen@gazlene.net","username":"krinkle"},"change_message_id":"21b48b63f23e61ad4f353349504639b88337e32c","unresolved":false,"context_lines":[{"line_number":412,"context_line":"`Enhance trusts`_ by detaching them from Users. Trusts still require role"},{"line_number":413,"context_line":"assignments on projects to be created by administrators. Adding the ability to"},{"line_number":414,"context_line":"allow users to delegate their own roles to trusts would require a much more"},{"line_number":415,"context_line":"significant rework of the trusts model."},{"line_number":416,"context_line":""},{"line_number":417,"context_line":"On naming: GCE uses the term \"Service Account\" and discusses the concept of"},{"line_number":418,"context_line":"\"Application Access\". Both could be useful alternate terms to Application"}],"source_content_type":"text/x-rst","patch_set":6,"id":"ff82abbf_b606aecd","line":415,"updated":"2017-11-27 23:24:41.000000000","message":"I\u0027m not sure I buy this. \"still require role assignments on projects to be created by administrators\" is not changing here, and I already can delegate my own roles to trusts. I can even create a trust for myself with a subset of the roles I have on a project. I think whatever we come up with here will end up just being a different front-end for trusts.","commit_id":"bb72c4899bd3d4f33f9ae803726ce615133ec58a"},{"author":{"_account_id":8482,"name":"Colleen Murphy","email":"colleen@gazlene.net","username":"krinkle"},"change_message_id":"f96f2fefd6f6a5422131d661935f3327ec7bf6fc","unresolved":false,"context_lines":[{"line_number":169,"context_line":"Date Time Format`_ and is assumed to be in UTC if an explicit timezone offset"},{"line_number":170,"context_line":"is not included."},{"line_number":171,"context_line":""},{"line_number":172,"context_line":"`roles` is an optional list of role names that is a subset of the roles"},{"line_number":173,"context_line":"the Creating User has on the Project to which they are scoped at creation time."},{"line_number":174,"context_line":"Roles that the Creating User does not have on the Project are an error."},{"line_number":175,"context_line":""}],"source_content_type":"text/x-rst","patch_set":8,"id":"ff82abbf_0152963b","line":172,"range":{"start_line":172,"start_character":14,"end_line":172,"end_character":41},"updated":"2017-11-28 22:22:17.000000000","message":"This should probably behave the same way trusts behave (as of today now that we fixed it) - it\u0027s an array of objects with one key, either id or name","commit_id":"63345eb701eb181332dbaff54fa42c498c13243f"}]}
