{"push_id":702550298,"size":2,"distinct_size":1,"ref":"refs/heads/saml-pp-squashed","head":"faa02452b89662e4239a760a5e9dd37040a88d17","before":"2721bf0cffbd1b99bc9ced44697be32e4b52c41e","commits":[{"sha":"eb904cd8fde640599fda87271729f53aa8022313","author":{"email":"0c11e55e6a36a8185db5745ba7416a2dde0b12ba@onecht.net","name":"Daan Hoogland"},"message":"findbugs: repeated condition seems c&p error the tested states sugest that EXPUNGED should be the last one\n\nSigned-off-by: Rohit Yadav <rohit.yadav@shapeblue.com>\n\nThis closes #491\n\n(cherry picked from commit bb613baa2b716dfe9aa7aed08b6cdd2027395456)\nSigned-off-by: Rohit Yadav <rohit.yadav@shapeblue.com>","distinct":false,"url":"https://api.github.com/repos/apache/cloudstack/commits/eb904cd8fde640599fda87271729f53aa8022313"},{"sha":"faa02452b89662e4239a760a5e9dd37040a88d17","author":{"email":"902b9eb5dd62819678163bd5e00fbf0cbc7c264b@shapeblue.com","name":"Rohit Yadav"},"message":"CLOUDSTACK-8457: SAML auth plugin improvements for production usage\n\n* Move config options to SAML plugin\n  This moves all configuration options from Config.java to SAML auth manager. This\n  allows us to use the config framework.\n* Make SAML2UserAuthenticator validate SAML token in httprequest\n* Make logout API use ConfigKeys defined in saml auth manager\n* Before doing SAML auth, cleanup local states and cookies\n* Fix configurations in 4.5.1 to 4.5.2 upgrade path\n* Fail if idp has no sso URL defined\n* Add a default set of SAML SP cert for testing purposes\n  Now to enable and use saml, one needs to do a deploydb-saml after doing a deploydb\n\n- CLOUDSTACK-8458:\n    * On UI show dropdown list of discovered IdPs\n    * Support SAML Federation, where there may be more than one IdP\n        - New datastructure to hold metadata of SP or IdP\n        - Recursive processing of IdP metadata\n        - Fix login/logout APIs to get new interface and metadata data structure\n        - Add org/contact information to metadata\n        - Add new API: listIdps that returns list of all discovered IdPs\n        - Refactor and cleanup code and tests\n\n- CLOUDSTACK-8459:\n    * Add HTTP-POST binding to SP metadata\n    * Authn requests must use either HTTP POST/Artifact binding\n\n- CLOUDSTACK-8461:\n    * Use unspecified x509 cert as a fallback encryption/signing key\n      In case a IDP's metadata does not clearly say if their certificates need to be\n      used as signing or encryption and we don't find that, fallback to use the\n      unspecified key itself.\n\n- CLOUDSTACK-8462:\n    * SAML Auth plugin should not do authorization\n      This removes logic to create user if they don't exist. This strictly now\n      assumes that users have been already created/imported/authorized by admins.\n      As per SAML v2.0 spec section 4.1.2, the SP provider should create authn requests using\n      either HTTP POST or HTTP Artifact binding to transfer the message through a\n      user agent (browser in our case). The use of HTTP Redirect was one of the reasons\n      why this plugin failed to work for some IdP servers that enforce this.\n    * Add new User Source\n      By reusing the source field, we can find if a user has been SAML enabled or not.\n      The limitation is that, once say a user is imported by LDAP and then SAML\n      enabled - they won't be able to use LDAP for authentication\n    * UI should allow users to pass in domain they want to log into\n    * SAML users need to be authorized before they can authenticate\n        - New column entity to track saml entity id for a user\n        - Reusing source column to check if user is saml enabled or not\n        - Add new source types, saml2 and saml2disabled\n        - New table saml_token to solve the issue of multiple users across domains and\n          to enforce security by tracking authn token and checking the samlresponse for\n          the tokens\n        - Implement API: authorizeSamlSso to enable/disable saml authentication for a\n          user\n        - Stubs to implement saml token flushing/expiry\n\n- CLOUDSTACK-8463:\n    * Use username attribute specified in global setting\n      Use username attribute defined by admin from a global setting\n      In case of encrypted assertion/attributes:\n      - Decrypt them\n      - Check signature if provided to check authenticity of message using IdP's\n        public key and SP's private key\n      - Loop through attributes to find the username\n\n- CLOUDSTACK-8538:\n    * Add new global config for SAML request sig algorithm\n\n- CLOUDSTACK-8539:\n    * Add metadata refresh timer task and token expiring\n        - Fix domain path and save it to saml_tokens\n        - Expire hour old saml tokens\n        - Refresh metadata based on timer task\n        - Fix unit tests\n\nSigned-off-by: Rohit Yadav <rohit.yadav@shapeblue.com>","distinct":true,"url":"https://api.github.com/repos/apache/cloudstack/commits/faa02452b89662e4239a760a5e9dd37040a88d17"}]}