Page History

Bug Reference

serverASF JIRAkeyVersion 1:  Jirahttps://issues.apache.org/jira/browse/CLOUDSTACK-7083
JiraserverASF JIRAkeyCLOUDSTACK-8457Version 2: : https://issues.apache.org/jira/browse/CLOUDSTACK-8457

Branch

Version 1: saml2

Version 2: saml2-production-grade

...

• Support multiple IdP servers if a federated metadata is provided: JiraserverASF JIRAkey: https://issues.apache.org/jira/browse/CLOUDSTACK-8458
• Support multiple endpoint bindings such as HTTP-Post:  JiraserverASF JIRAkeyCLOUDSTACK-8459: https://issues.apache.org/jira/browse/CLOUDSTACK-8459
• Survey and support standard IdP servers such as Shibboleth 2.4+:   JiraserverASF JIRAkeyCLOUDSTACK-8460https://issues.apache.org/jira/browse/CLOUDSTACK-8460
• Ensure compability as per the saml2int.org standards:  JiraserverASF JIRAkeyCLOUDSTACK-8461: https://issues.apache.org/jira/browse/CLOUDSTACK-8461
• Don't depend on NameId for getting unique ID (it could be a non-static one like urn:oasis:names:tc:SAML:2.0:nameid-format:transient), instead depend on an admin specified attribute:  JiraserverASF JIRAkeyCLOUDSTACK-8463: https://issues.apache.org/jira/browse/CLOUDSTACK-8463
• Let admin add/import and configure the user, the plugin should only check authorization. In case of multiple allowed SAML users with same username, authenticated user should be allowed to use any of the available account in any domain:   JiraserverASF JIRAkeyCLOUDSTACK-8462 https://issues.apache.org/jira/browse/CLOUDSTACK-8462
  
• Allow admins to save IdP metadata on filesystem or in DB:  JiraserverASF JIRAkeyCLOUDSTACK-8464: https://issues.apache.org/jira/browse/CLOUDSTACK-8464
• Improve UI for SAML authentication, currently a button is visible if saml plugin is enabled. We need to have a dropdown list of IdPs in case of multiple IdPs.
• Address any open-ended questions and production usage
• Get some field testing done
• Document the improved plugin usage

...