Enterprise SAML for SAML 2.0 and 1.1 SSO – What is required?
As SAML demand grows, the demand for comprehensive Enterprise Class SAML Product solutions that support SAML 2.0 and SAML 1.1 is also growing very quickly.
What is required for an Enterprise Class SAML Single Sign On (SSO) Product?
- Fast, easy implementation of SAML connections
- SAML product must be configuration based
- SAML deployments completed without becoming a SAML expert
- No custom coding required for SAML deployments
- No consulting assistance required to enable SAML deployments
- Multiple platform support
- .Net and Java/J2EE are most critical
- Broad platform support provided with the SAML product out of the box
- Multiple SAML Connection support
- Must be designed for effective and efficient enablement and support of multiple SAML connections
- Multiple protocol support
- Must have the ability to support SAML 2.0 and SAML 1.1 use cases and connections
- Must provide this type of multi-protocol support within a single implementation of the enterprise SAML software product implementation, with support for central management of multiple disparate SAML protocol connections
- Multiple use case support
- Must support various Identity Provider (IDP) and Service Provider (SP) use cases, very easily
- Affordable
- Licensing must be affordable
- Licensing must allow clients to start small, and pay a little
- Licensing costs cannot become prohibitive with broad deployments
Tags: SAML 1.1 .NET,
SAML 1.1 J2EE,
SAML 1.1 Java,
SAML 2.0,
SAML 2.0 .NET,
SAML 2.0 J2EE,
SAML 2.0 JAVA