)]}'
{"specs/keystone/ocata/per-user-auth-plugin-requirements.rst":[{"author":{"_account_id":7725,"name":"David Stanek","email":"dstanek@dstanek.com","username":"dstanek"},"change_message_id":"1bf5d65545670933414255726ab2d48d25a8a024","unresolved":false,"context_lines":[{"line_number":11,"context_line":"`bp per-user-auth-plugin-reqs \u003chttps://blueprints.launchpad.net/keystone/+spec/per-user-auth-plugin-reqs\u003e`_"},{"line_number":12,"context_line":""},{"line_number":13,"context_line":""},{"line_number":14,"context_line":"Keystone should be able to support the ability to require (on a per-user basis)"},{"line_number":15,"context_line":"the authentication plugins (the ones supported in the keystone server) that"},{"line_number":16,"context_line":"are required to authenticate."},{"line_number":17,"context_line":""}],"source_content_type":"text/x-rst","patch_set":4,"id":"3a71b18c_481c7d13","line":14,"updated":"2016-12-02 14:19:08.000000000","message":"This supports the github-like case where a user can opt-in to protect their account. Is there any support for cases where an operator wants to for all Members to use certain plugins? (Aside from changing their provisioning processes.)","commit_id":"dd682b797f38deb807747964642571e2495062d2"},{"author":{"_account_id":7725,"name":"David Stanek","email":"dstanek@dstanek.com","username":"dstanek"},"change_message_id":"e93ab4e1757bb5f2149b0a1d673d9aad3da89374","unresolved":false,"context_lines":[{"line_number":11,"context_line":"`bp per-user-auth-plugin-reqs \u003chttps://blueprints.launchpad.net/keystone/+spec/per-user-auth-plugin-reqs\u003e`_"},{"line_number":12,"context_line":""},{"line_number":13,"context_line":""},{"line_number":14,"context_line":"Keystone should be able to support the ability to require (on a per-user basis)"},{"line_number":15,"context_line":"the authentication plugins (the ones supported in the keystone server) that"},{"line_number":16,"context_line":"are required to authenticate."},{"line_number":17,"context_line":""}],"source_content_type":"text/x-rst","patch_set":4,"id":"3a71b18c_e92f083c","line":14,"in_reply_to":"3a71b18c_0ee8cab3","updated":"2016-12-02 16:17:06.000000000","message":"Fair enough. I figured the provisioning change would be the answer. When I originally thought about MFA I was thinking it would be group based, but that\u0027s not enough flexibility.","commit_id":"dd682b797f38deb807747964642571e2495062d2"},{"author":{"_account_id":2903,"name":"Morgan Fainberg","email":"morgan.fainberg@gmail.com","username":"mdrnstm"},"change_message_id":"a7534fabb66f95b002cb3f4c37038432d61237b2","unresolved":false,"context_lines":[{"line_number":11,"context_line":"`bp per-user-auth-plugin-reqs \u003chttps://blueprints.launchpad.net/keystone/+spec/per-user-auth-plugin-reqs\u003e`_"},{"line_number":12,"context_line":""},{"line_number":13,"context_line":""},{"line_number":14,"context_line":"Keystone should be able to support the ability to require (on a per-user basis)"},{"line_number":15,"context_line":"the authentication plugins (the ones supported in the keystone server) that"},{"line_number":16,"context_line":"are required to authenticate."},{"line_number":17,"context_line":""}],"source_content_type":"text/x-rst","patch_set":4,"id":"3a71b18c_0ee8cab3","line":14,"in_reply_to":"3a71b18c_481c7d13","updated":"2016-12-02 16:07:28.000000000","message":"The answer to that is to change the provisioning process for now or to use an auth plugin that has more business logic in it.\n\nWe could add a \"default\" in, but by adding in a default rule it is highly possibly to simply break a cloud. \n\nWe could add a \"default\" ruleset like support if that is a requirement to land this. I am unsure if that makes sense here or if it makes sense to add that on once this core bit of code is landed.","commit_id":"dd682b797f38deb807747964642571e2495062d2"},{"author":{"_account_id":7725,"name":"David Stanek","email":"dstanek@dstanek.com","username":"dstanek"},"change_message_id":"1bf5d65545670933414255726ab2d48d25a8a024","unresolved":false,"context_lines":[{"line_number":37,"context_line":"configured, the current default of \"any single auth plugin configured in"},{"line_number":38,"context_line":"keystone.conf\" will continue to work."},{"line_number":39,"context_line":""},{"line_number":40,"context_line":"The rules will be represented in JSON:"},{"line_number":41,"context_line":""},{"line_number":42,"context_line":".. code-block:: json"},{"line_number":43,"context_line":""}],"source_content_type":"text/x-rst","patch_set":4,"id":"3a71b18c_9d609537","line":40,"updated":"2016-12-02 14:19:08.000000000","message":"What resource will included these? I\u0027m guessing they\u0027d at least be in the 4xx that gets returned if they do not include the correct plugin data.","commit_id":"dd682b797f38deb807747964642571e2495062d2"},{"author":{"_account_id":2903,"name":"Morgan Fainberg","email":"morgan.fainberg@gmail.com","username":"mdrnstm"},"change_message_id":"ffb2bbb4e690eef33a24702de39dd10ae9f89832","unresolved":false,"context_lines":[{"line_number":37,"context_line":"configured, the current default of \"any single auth plugin configured in"},{"line_number":38,"context_line":"keystone.conf\" will continue to work."},{"line_number":39,"context_line":""},{"line_number":40,"context_line":"The rules will be represented in JSON:"},{"line_number":41,"context_line":""},{"line_number":42,"context_line":".. code-block:: json"},{"line_number":43,"context_line":""}],"source_content_type":"text/x-rst","patch_set":4,"id":"3a71b18c_a4b53532","line":40,"in_reply_to":"3a71b18c_9d609537","updated":"2016-12-02 16:26:46.000000000","message":"These rules will be included on the user object? I guess that doesn\u0027t work with federated auth. It needs to be a separate mapping table of user_id - to - rule?","commit_id":"dd682b797f38deb807747964642571e2495062d2"},{"author":{"_account_id":7725,"name":"David Stanek","email":"dstanek@dstanek.com","username":"dstanek"},"change_message_id":"1bf5d65545670933414255726ab2d48d25a8a024","unresolved":false,"context_lines":[{"line_number":51,"context_line":"the database schema as a ``blob`` type (serialized as JSON)."},{"line_number":52,"context_line":""},{"line_number":53,"context_line":"In the case that a required plugin is configured but is not enabled in the"},{"line_number":54,"context_line":"Keystone.conf, that part of the rule is simply ignored (e.g. \"password AND"},{"line_number":55,"context_line":"totp\" is the rule, but keystone.conf only has \"password\" enabled, \"totp\" will"},{"line_number":56,"context_line":"simply be ignored as a requirement for authentication purposes for any/all"},{"line_number":57,"context_line":"users)."}],"source_content_type":"text/x-rst","patch_set":4,"id":"3a71b18c_3d50615e","line":54,"updated":"2016-12-02 14:19:08.000000000","message":"k","commit_id":"dd682b797f38deb807747964642571e2495062d2"},{"author":{"_account_id":7725,"name":"David Stanek","email":"dstanek@dstanek.com","username":"dstanek"},"change_message_id":"1bf5d65545670933414255726ab2d48d25a8a024","unresolved":false,"context_lines":[{"line_number":54,"context_line":"Keystone.conf, that part of the rule is simply ignored (e.g. \"password AND"},{"line_number":55,"context_line":"totp\" is the rule, but keystone.conf only has \"password\" enabled, \"totp\" will"},{"line_number":56,"context_line":"simply be ignored as a requirement for authentication purposes for any/all"},{"line_number":57,"context_line":"users)."},{"line_number":58,"context_line":""},{"line_number":59,"context_line":"If there is only one plugin \"required\" for a user and that plugin is"},{"line_number":60,"context_line":"disabled keystone will fall back to the default behavior of \"any one plugin"}],"source_content_type":"text/x-rst","patch_set":4,"id":"3a71b18c_7d8f39cc","line":57,"updated":"2016-12-02 14:19:08.000000000","message":"If they are ignored they won\u0027t appear in the JSON output right?","commit_id":"dd682b797f38deb807747964642571e2495062d2"},{"author":{"_account_id":2903,"name":"Morgan Fainberg","email":"morgan.fainberg@gmail.com","username":"mdrnstm"},"change_message_id":"a7534fabb66f95b002cb3f4c37038432d61237b2","unresolved":false,"context_lines":[{"line_number":54,"context_line":"Keystone.conf, that part of the rule is simply ignored (e.g. \"password AND"},{"line_number":55,"context_line":"totp\" is the rule, but keystone.conf only has \"password\" enabled, \"totp\" will"},{"line_number":56,"context_line":"simply be ignored as a requirement for authentication purposes for any/all"},{"line_number":57,"context_line":"users)."},{"line_number":58,"context_line":""},{"line_number":59,"context_line":"If there is only one plugin \"required\" for a user and that plugin is"},{"line_number":60,"context_line":"disabled keystone will fall back to the default behavior of \"any one plugin"}],"source_content_type":"text/x-rst","patch_set":4,"id":"3a71b18c_2ed586b8","line":57,"in_reply_to":"3a71b18c_7d8f39cc","updated":"2016-12-02 16:07:28.000000000","message":"Correct.\n\nI actually think keystone rejects the auth request if the plugin is not enabled in keystone. I can 2x check. \n\nIn either case, the only values in the JSON would be plugins that are actually processed in the auth request. This \"ignore\" is simply for the sake of ensuring that if keystone.conf is disabling TOTP, a user can\u0027t lock themselves out of the cloud because TOTP was previously \"required\"","commit_id":"dd682b797f38deb807747964642571e2495062d2"},{"author":{"_account_id":7725,"name":"David Stanek","email":"dstanek@dstanek.com","username":"dstanek"},"change_message_id":"e93ab4e1757bb5f2149b0a1d673d9aad3da89374","unresolved":false,"context_lines":[{"line_number":58,"context_line":""},{"line_number":59,"context_line":"If there is only one plugin \"required\" for a user and that plugin is"},{"line_number":60,"context_line":"disabled keystone will fall back to the default behavior of \"any one plugin"},{"line_number":61,"context_line":"configured is sufficient\"."},{"line_number":62,"context_line":""},{"line_number":63,"context_line":"The authentication request will conform to the current keystone standard for"},{"line_number":64,"context_line":"multiple auth-plugin forms:"}],"source_content_type":"text/x-rst","patch_set":4,"id":"3a71b18c_89dcd413","line":61,"updated":"2016-12-02 16:17:06.000000000","message":"In the \"any one plugin\" scenario will the user know that one of their factors is disabled. For example, if they provide password/totp and totp is not enabled. I\u0027m not sure what we currently do. Either way it\u0027s probably something they should know.","commit_id":"dd682b797f38deb807747964642571e2495062d2"},{"author":{"_account_id":2903,"name":"Morgan Fainberg","email":"morgan.fainberg@gmail.com","username":"mdrnstm"},"change_message_id":"91f110c0a8ec26128b4a1b4b76aa4888b019232a","unresolved":false,"context_lines":[{"line_number":58,"context_line":""},{"line_number":59,"context_line":"If there is only one plugin \"required\" for a user and that plugin is"},{"line_number":60,"context_line":"disabled keystone will fall back to the default behavior of \"any one plugin"},{"line_number":61,"context_line":"configured is sufficient\"."},{"line_number":62,"context_line":""},{"line_number":63,"context_line":"The authentication request will conform to the current keystone standard for"},{"line_number":64,"context_line":"multiple auth-plugin forms:"}],"source_content_type":"text/x-rst","patch_set":4,"id":"3a71b18c_c9bc0c6f","line":61,"in_reply_to":"3a71b18c_89dcd413","updated":"2016-12-02 16:23:46.000000000","message":"Like i said, I\u0027m pretty sure keystone rejects this auth request with an \"unknown auth-type XXX\" response. \n\nhttps://github.com/openstack/keystone/blob/796a61715f760fa4db1fe4d760e84f7683386b9a/keystone/auth/controllers.py#L87-L89\n\nWe should make sure this is passed back to the user.","commit_id":"dd682b797f38deb807747964642571e2495062d2"},{"author":{"_account_id":7725,"name":"David Stanek","email":"dstanek@dstanek.com","username":"dstanek"},"change_message_id":"1bf5d65545670933414255726ab2d48d25a8a024","unresolved":false,"context_lines":[{"line_number":94,"context_line":"    }"},{"line_number":95,"context_line":""},{"line_number":96,"context_line":"If insufficient auth plugins are supplied a ``HTTP 401`` with a JSON response"},{"line_number":97,"context_line":"indicating insufficient auth parameters will be returned to the request0r. This"},{"line_number":98,"context_line":"response will be the same regardless of correct-ness of any of the"},{"line_number":99,"context_line":"values passed to the authentication plugins. The plugins used for a given"},{"line_number":100,"context_line":"request compared to the plugin data supplied will be compared prior to"}],"source_content_type":"text/x-rst","patch_set":4,"id":"3a71b18c_dd3bede9","line":97,"updated":"2016-12-02 14:19:08.000000000","message":"requestor","commit_id":"dd682b797f38deb807747964642571e2495062d2"},{"author":{"_account_id":2903,"name":"Morgan Fainberg","email":"morgan.fainberg@gmail.com","username":"mdrnstm"},"change_message_id":"a7534fabb66f95b002cb3f4c37038432d61237b2","unresolved":false,"context_lines":[{"line_number":94,"context_line":"    }"},{"line_number":95,"context_line":""},{"line_number":96,"context_line":"If insufficient auth plugins are supplied a ``HTTP 401`` with a JSON response"},{"line_number":97,"context_line":"indicating insufficient auth parameters will be returned to the request0r. This"},{"line_number":98,"context_line":"response will be the same regardless of correct-ness of any of the"},{"line_number":99,"context_line":"values passed to the authentication plugins. The plugins used for a given"},{"line_number":100,"context_line":"request compared to the plugin data supplied will be compared prior to"}],"source_content_type":"text/x-rst","patch_set":4,"id":"3a71b18c_4e03a242","line":97,"in_reply_to":"3a71b18c_dd3bede9","updated":"2016-12-02 16:07:28.000000000","message":"fixed in next patch","commit_id":"dd682b797f38deb807747964642571e2495062d2"},{"author":{"_account_id":7725,"name":"David Stanek","email":"dstanek@dstanek.com","username":"dstanek"},"change_message_id":"1bf5d65545670933414255726ab2d48d25a8a024","unresolved":false,"context_lines":[{"line_number":96,"context_line":"If insufficient auth plugins are supplied a ``HTTP 401`` with a JSON response"},{"line_number":97,"context_line":"indicating insufficient auth parameters will be returned to the request0r. This"},{"line_number":98,"context_line":"response will be the same regardless of correct-ness of any of the"},{"line_number":99,"context_line":"values passed to the authentication plugins. The plugins used for a given"},{"line_number":100,"context_line":"request compared to the plugin data supplied will be compared prior to"},{"line_number":101,"context_line":"validating the data supplied to the plugins."},{"line_number":102,"context_line":""}],"source_content_type":"text/x-rst","patch_set":4,"id":"3a71b18c_1d0d653e","line":99,"updated":"2016-12-02 14:19:08.000000000","message":"s/used/required/ ?","commit_id":"dd682b797f38deb807747964642571e2495062d2"},{"author":{"_account_id":2903,"name":"Morgan Fainberg","email":"morgan.fainberg@gmail.com","username":"mdrnstm"},"change_message_id":"a7534fabb66f95b002cb3f4c37038432d61237b2","unresolved":false,"context_lines":[{"line_number":96,"context_line":"If insufficient auth plugins are supplied a ``HTTP 401`` with a JSON response"},{"line_number":97,"context_line":"indicating insufficient auth parameters will be returned to the request0r. This"},{"line_number":98,"context_line":"response will be the same regardless of correct-ness of any of the"},{"line_number":99,"context_line":"values passed to the authentication plugins. The plugins used for a given"},{"line_number":100,"context_line":"request compared to the plugin data supplied will be compared prior to"},{"line_number":101,"context_line":"validating the data supplied to the plugins."},{"line_number":102,"context_line":""}],"source_content_type":"text/x-rst","patch_set":4,"id":"3a71b18c_ae8fd6ca","line":99,"in_reply_to":"3a71b18c_1d0d653e","updated":"2016-12-02 16:07:28.000000000","message":"Fixed in next.","commit_id":"dd682b797f38deb807747964642571e2495062d2"},{"author":{"_account_id":7725,"name":"David Stanek","email":"dstanek@dstanek.com","username":"dstanek"},"change_message_id":"1bf5d65545670933414255726ab2d48d25a8a024","unresolved":false,"context_lines":[{"line_number":132,"context_line":"Notifications Impact"},{"line_number":133,"context_line":"--------------------"},{"line_number":134,"context_line":""},{"line_number":135,"context_line":"NONE"},{"line_number":136,"context_line":""},{"line_number":137,"context_line":"Other End User Impact"},{"line_number":138,"context_line":"---------------------"}],"source_content_type":"text/x-rst","patch_set":4,"id":"3a71b18c_0880c545","line":135,"updated":"2016-12-02 14:19:08.000000000","message":"Probably some new notifications, particularly the scenario when a user has no valid auth plugins rules.","commit_id":"dd682b797f38deb807747964642571e2495062d2"},{"author":{"_account_id":2903,"name":"Morgan Fainberg","email":"morgan.fainberg@gmail.com","username":"mdrnstm"},"change_message_id":"a7534fabb66f95b002cb3f4c37038432d61237b2","unresolved":false,"context_lines":[{"line_number":132,"context_line":"Notifications Impact"},{"line_number":133,"context_line":"--------------------"},{"line_number":134,"context_line":""},{"line_number":135,"context_line":"NONE"},{"line_number":136,"context_line":""},{"line_number":137,"context_line":"Other End User Impact"},{"line_number":138,"context_line":"---------------------"}],"source_content_type":"text/x-rst","patch_set":4,"id":"3a71b18c_e902a808","line":135,"in_reply_to":"3a71b18c_0880c545","updated":"2016-12-02 16:07:28.000000000","message":"If there are no valid plugin rules, it would be today\u0027s auth workflow (any single auth plugin can be used, provided the user can actually auth with it). I could log this, I am unsure if we need notifications here.\n\nPlease expand on why you want that to be a notification and I can add it. I don\u0027t see it as a CADF event.","commit_id":"dd682b797f38deb807747964642571e2495062d2"},{"author":{"_account_id":2903,"name":"Morgan Fainberg","email":"morgan.fainberg@gmail.com","username":"mdrnstm"},"change_message_id":"91f110c0a8ec26128b4a1b4b76aa4888b019232a","unresolved":false,"context_lines":[{"line_number":132,"context_line":"Notifications Impact"},{"line_number":133,"context_line":"--------------------"},{"line_number":134,"context_line":""},{"line_number":135,"context_line":"NONE"},{"line_number":136,"context_line":""},{"line_number":137,"context_line":"Other End User Impact"},{"line_number":138,"context_line":"---------------------"}],"source_content_type":"text/x-rst","patch_set":4,"id":"3a71b18c_0945246f","line":135,"in_reply_to":"3a71b18c_89a054a1","updated":"2016-12-02 16:23:46.000000000","message":"I view that as a warning (maybe info?) level log.\n\nAs a point the API wont let users set auth plugins that are not enabled. I can add a line in the spec to that regard. It is an administrative fix in the case that a plugin is being \"permanently\" disabled.\n\nI definitely don\u0027t want to spam the bus with more notifications for each auth attempt.","commit_id":"dd682b797f38deb807747964642571e2495062d2"},{"author":{"_account_id":7725,"name":"David Stanek","email":"dstanek@dstanek.com","username":"dstanek"},"change_message_id":"e93ab4e1757bb5f2149b0a1d673d9aad3da89374","unresolved":false,"context_lines":[{"line_number":132,"context_line":"Notifications Impact"},{"line_number":133,"context_line":"--------------------"},{"line_number":134,"context_line":""},{"line_number":135,"context_line":"NONE"},{"line_number":136,"context_line":""},{"line_number":137,"context_line":"Other End User Impact"},{"line_number":138,"context_line":"---------------------"}],"source_content_type":"text/x-rst","patch_set":4,"id":"3a71b18c_89a054a1","line":135,"in_reply_to":"3a71b18c_e902a808","updated":"2016-12-02 16:17:06.000000000","message":"I don\u0027t know how likely it is to happen, but there is a disconnect between what is enabled in the config and what the user can set. Since there is a fallback mechanism the user will be OK, but I was just thinking that an operator would want to know.","commit_id":"dd682b797f38deb807747964642571e2495062d2"},{"author":{"_account_id":10420,"name":"Adrian Turjak","email":"devs+openstack@uncaught-exceptions.com","username":"adriant"},"change_message_id":"62086b7ea517eceb890e4ba9c72bafead4848393","unresolved":false,"context_lines":[{"line_number":150,"context_line":"Other Deployer Impact"},{"line_number":151,"context_line":"---------------------"},{"line_number":152,"context_line":""},{"line_number":153,"context_line":"Deployers wishing to enforce use of multiple auth-types will need to"},{"line_number":154,"context_line":"create the users with the new rules (and/or update current users). If the"},{"line_number":155,"context_line":"deployer does not want users to update the auth-plugin requirements, policy"},{"line_number":156,"context_line":"will need to be updated to deny access to the new self-service"},{"line_number":157,"context_line":"auth-plugin-requirements API."},{"line_number":158,"context_line":""},{"line_number":159,"context_line":"Developer Impact"},{"line_number":160,"context_line":"----------------"}],"source_content_type":"text/x-rst","patch_set":4,"id":"3a71b18c_44819ec2","line":157,"range":{"start_line":153,"start_character":0,"end_line":157,"end_character":29},"updated":"2016-12-04 22:35:54.000000000","message":"Mostly this is fine, but my worry is the case where you want to  disallow a certain plugin by itself. As a deployer and an admin I would hate to be forced to give everyone a rule to this effect.\n\nAssuming I have the following active:\n\"external,password,token,totp\"\n\nI don\u0027t ever want totp used by itself. But... I need it active, and this spec assumes the default is \"any one of active plugins\" as it used to be.\n\nI can limit the new API to admin only, and users will have to manage their rules via an external service where I can disallow them from setting totp by itself as a rule. The problem is that for all new users I need to set \"any one of active expect totp\", which is a hassle and not exactly a good way of doing it.\n\nHaving an optional global default rule is much better, and so it doesn\u0027t break anything we can do.\n\nif user has rules:\n     use those\nelif conf has rules:\n     use those\nelse:\n    \"one of any active auth plugin\"\n\nThis would provide full backward compatibility while giving more power to deployers without the need to insert default rules at user creation.\n\nNot to mention a deployer wanting to change default rules would have no good way of doing so because all existing users would have rules and editing those would be unsafe. A global default change would still affect all users without rules while avoiding any unsafe per user rule editing.","commit_id":"dd682b797f38deb807747964642571e2495062d2"},{"author":{"_account_id":10420,"name":"Adrian Turjak","email":"devs+openstack@uncaught-exceptions.com","username":"adriant"},"change_message_id":"eb75fea4753c4dfc58949263e695d3f5aa6ee725","unresolved":false,"context_lines":[{"line_number":150,"context_line":"Other Deployer Impact"},{"line_number":151,"context_line":"---------------------"},{"line_number":152,"context_line":""},{"line_number":153,"context_line":"Deployers wishing to enforce use of multiple auth-types will need to"},{"line_number":154,"context_line":"create the users with the new rules (and/or update current users). If the"},{"line_number":155,"context_line":"deployer does not want users to update the auth-plugin requirements, policy"},{"line_number":156,"context_line":"will need to be updated to deny access to the new self-service"},{"line_number":157,"context_line":"auth-plugin-requirements API."},{"line_number":158,"context_line":""},{"line_number":159,"context_line":"Developer Impact"},{"line_number":160,"context_line":"----------------"}],"source_content_type":"text/x-rst","patch_set":4,"id":"3a71b18c_43424269","line":157,"range":{"start_line":153,"start_character":0,"end_line":157,"end_character":29},"in_reply_to":"3a71b18c_17d412bb","updated":"2016-12-06 00:27:38.000000000","message":"I was thinking in keystone itself we never set a default. That falls entirely on the deployer. The \u0027default\u0027 in keystone is none, so \"any one of the active plugins\".\n\nI mean, we could always throw in some warnings or start-up check that validates the default makes sense. Doing a check for \"does default rule contain plugins not actually enabled\" is easy, but ignoring that part of the rule if the plugin isn\u0027t configured may be hard to debug from a deployer perspective, so it might be better to log warnings or not start at all if the conf is misconfigured.\n\nEven as it stands, we don\u0027t have a good way of doing \"is totp configured\" other than the user rules themselves. If an admin sets that rule for you on user creation, the user is just as locked out as if the deployer had set a rule via the global default so really it is up to admin/deployer not misuse the rules or setup bad defaults. I think the usefulness of an optional global default far outweighs the situation where users get bitten by a mistake on the deployers part.\n\nAlthough what you\u0027re talking about in regards to opt-in sounds a lot like what I was trying to do with just TOTP with this spec:\nhttps://review.openstack.org/#/c/345705\n\nSo for the self service rules API are you thinking something like my user managed totp spec, but for all plugins and rules? Not exactly sure how to make such and API actually maintainable without doing a new mini API for each plugin/auth type that needs to be setup/activated differently. Or were you thinking setup new rules in a sort of pending state, and only when you actually auth for the first time with your pending rules does it enabled it?\n\nIn either case, if we do self management of rules we probably will need to consider some vague business logic where a deployer doesn\u0027t want a user to set unsafe rules themselves. Maybe a set of configurable rule options rather than giving a user full access to their rules.\nExample:\nactive\u003d\"password,totp,external,oath1\",\ndefault\u003d\"password,external,oath1\",\nuser sets: user_rules\u003d\"totp\"\nWhen really the deployer only wants the user to be able to give themselves rules like: \"\u003cother_auth\u003e+totp\"","commit_id":"dd682b797f38deb807747964642571e2495062d2"},{"author":{"_account_id":2903,"name":"Morgan Fainberg","email":"morgan.fainberg@gmail.com","username":"mdrnstm"},"change_message_id":"d26296c3fd63a2614e1cef3abb14d7c0286f570c","unresolved":false,"context_lines":[{"line_number":150,"context_line":"Other Deployer Impact"},{"line_number":151,"context_line":"---------------------"},{"line_number":152,"context_line":""},{"line_number":153,"context_line":"Deployers wishing to enforce use of multiple auth-types will need to"},{"line_number":154,"context_line":"create the users with the new rules (and/or update current users). If the"},{"line_number":155,"context_line":"deployer does not want users to update the auth-plugin requirements, policy"},{"line_number":156,"context_line":"will need to be updated to deny access to the new self-service"},{"line_number":157,"context_line":"auth-plugin-requirements API."},{"line_number":158,"context_line":""},{"line_number":159,"context_line":"Developer Impact"},{"line_number":160,"context_line":"----------------"}],"source_content_type":"text/x-rst","patch_set":4,"id":"3a71b18c_70443449","line":157,"range":{"start_line":153,"start_character":0,"end_line":157,"end_character":29},"in_reply_to":"3a71b18c_43424269","updated":"2016-12-06 19:22:14.000000000","message":"The self service API would require the same payload (information) as an auth request for each plugin specified (regardless of the number of times).\n\nIf you request totp, password, and x509 for example, you\u0027d have a separate section that is passed (or the data is populated by apache in cases such as x509) that run the auth plugin logic. If the plugin fails, the new ruleset is rejected.\n\nAdding an auth plugin ruleset would require a token. This isn\u0027t special business logic per plugin, it\u0027s just running the plugin logic to make sure it has received sane data.\n\nI am going to punt on the \"default\" rules to start. Ocata is a short cycle. Lets get the basic feature set in. We can add default rules (capability) as a followup.","commit_id":"dd682b797f38deb807747964642571e2495062d2"},{"author":{"_account_id":2903,"name":"Morgan Fainberg","email":"morgan.fainberg@gmail.com","username":"mdrnstm"},"change_message_id":"057b4f2781c3d66c9c2d315b151e4116ae94e047","unresolved":false,"context_lines":[{"line_number":150,"context_line":"Other Deployer Impact"},{"line_number":151,"context_line":"---------------------"},{"line_number":152,"context_line":""},{"line_number":153,"context_line":"Deployers wishing to enforce use of multiple auth-types will need to"},{"line_number":154,"context_line":"create the users with the new rules (and/or update current users). If the"},{"line_number":155,"context_line":"deployer does not want users to update the auth-plugin requirements, policy"},{"line_number":156,"context_line":"will need to be updated to deny access to the new self-service"},{"line_number":157,"context_line":"auth-plugin-requirements API."},{"line_number":158,"context_line":""},{"line_number":159,"context_line":"Developer Impact"},{"line_number":160,"context_line":"----------------"}],"source_content_type":"text/x-rst","patch_set":4,"id":"3a71b18c_17d412bb","line":157,"range":{"start_line":153,"start_character":0,"end_line":157,"end_character":29},"in_reply_to":"3a71b18c_44819ec2","updated":"2016-12-05 18:00:51.000000000","message":"Absolutely possible to block the new api (self-service) for users via policy and having a user manage these things via an external service (which would make use of \"update user\" instead of the self-service API).\n\nIt should be easy enough to add a global \"default\" rule, but I\u0027m going to assert it still requires the plugins to be enabled in keystone.conf.\n\nThe main reason I see the default rule as problematic is that it doesn\u0027t look at things such as \"is totp configured\", it will only be looking at *if* totp is specified as an auth plugin (and passes correct values for authn). This means that if a user has \"TOTP\" required (aka via a default) and does not have a TOTP credential, they will be unable to authenticate since the TOTP plugin will not validate the input (it fails auth).\n\nI was taking the view of \"opt-in\" which can (with the self-service api) require sending auth information which is validated (password, totp token, etc) to \"enable\" it as a required mechanism.\n\nIn the case of the external system, since \"update user\" (admin function) is utilized, it will be on that external system to validate the information prior to setting the auth plugins.","commit_id":"dd682b797f38deb807747964642571e2495062d2"},{"author":{"_account_id":17860,"name":"Samuel de Medeiros Queiroz","email":"samueldmq@gmail.com","username":"samueldmq"},"change_message_id":"0213068ef7a8214bca235134d98de388c6aacf1e","unresolved":false,"context_lines":[{"line_number":54,"context_line":"Keystone.conf, that part of the rule is simply ignored (e.g. \"password AND"},{"line_number":55,"context_line":"totp\" is the rule, but keystone.conf only has \"password\" enabled, \"totp\" will"},{"line_number":56,"context_line":"simply be ignored as a requirement for authentication purposes for any/all"},{"line_number":57,"context_line":"users)."},{"line_number":58,"context_line":""},{"line_number":59,"context_line":"If there is only one plugin \"required\" for a user and that plugin is"},{"line_number":60,"context_line":"disabled keystone will fall back to the default behavior of \"any one plugin"}],"source_content_type":"text/x-rst","patch_set":5,"id":"3a71b18c_73b27e4d","line":57,"updated":"2016-12-06 19:58:47.000000000","message":"And we at least LOG an warning to communicate the operator","commit_id":"a0f0fbe56cc039c70b7de530653a096db2ee062f"},{"author":{"_account_id":17860,"name":"Samuel de Medeiros Queiroz","email":"samueldmq@gmail.com","username":"samueldmq"},"change_message_id":"0213068ef7a8214bca235134d98de388c6aacf1e","unresolved":false,"context_lines":[{"line_number":127,"context_line":"Security Impact"},{"line_number":128,"context_line":"---------------"},{"line_number":129,"context_line":""},{"line_number":130,"context_line":"TBD"},{"line_number":131,"context_line":""},{"line_number":132,"context_line":"Notifications Impact"},{"line_number":133,"context_line":"--------------------"}],"source_content_type":"text/x-rst","patch_set":5,"id":"3a71b18c_b3c7b662","line":130,"range":{"start_line":130,"start_character":0,"end_line":130,"end_character":3},"updated":"2016-12-06 19:58:47.000000000","message":"I will propose a patch defining this section","commit_id":"a0f0fbe56cc039c70b7de530653a096db2ee062f"}]}
