For customers not using SSO, does your application support integration with other authentication and authorization systems?
Explanation
For customers who don't rely on SSO, the concern is whether your application can plug into authentication and authorization systems beyond your own native login. Authentication systems verify user identity (who they are), while authorization systems determine what they can access.
In security assessments, this question matters because:
1. Organizations often have existing identity management systems they want to leverage rather than creating separate credentials for each application.
2. Centralized authentication improves security by enabling consistent password policies, multi-factor authentication, and faster account deprovisioning when employees leave.
3. Integration with existing systems reduces 'identity sprawl' where users have multiple credentials across different systems, which increases security risks.
Authentication integration might include support for:
- LDAP (Lightweight Directory Access Protocol)
- Active Directory
- OAuth/OpenID Connect
- SAML (beyond traditional SSO implementations)
- Custom API-based authentication
- Radius or other network authentication protocols
When answering, be specific about which authentication systems you support, any limitations, and whether these integrations are included in your base product or require additional configuration/cost.
Example Responses
Example Response 1
Yes, our application supports multiple authentication integration options beyond SSO We support LDAP/Active Directory integration for enterprise customers, allowing them to use their existing directory services We also support OAuth 2.0 and OpenID Connect for integration with identity providers like Auth0, Okta, and Microsoft Entra ID (formerly Azure AD) Additionally, we offer a REST API authentication framework that allows customers to build custom authentication integrations with proprietary systems All these integration options are included in our enterprise tier subscription at no additional cost, though custom implementation services are available if needed.
Example Response 2
Yes, our application supports integration with several third-party authentication systems We currently support SAML 2.0 (which can be used beyond typical SSO implementations), LDAP bind authentication, and OAuth 2.0 flows For customers with more complex needs, we provide an authentication plugin framework that allows for custom authentication provider development We've successfully deployed custom authentication integrations with biometric systems, smart cards, and proprietary enterprise authentication systems Documentation and implementation guides for all supported authentication methods are available in our developer portal.
Example Response 3
No, our application currently only supports our native username/password authentication system and standard SAML-based SSO We do not currently support integration with other authentication systems like LDAP, Active Directory, or OAuth This limitation exists because our application was originally designed for small businesses without complex identity infrastructure We recognize this as a gap in our offering and have planned to add LDAP and OAuth support in our Q3 product roadmap this year For customers requiring these integrations immediately, we recommend using identity broker services that can translate between SAML (which we do support) and other authentication protocols.
Context
- Tab
- Product
- Category
- Authentication, Authorization, and Account Management
Related questions
- Does your solution support single sign-on (SSO) protocols for user and administrator authentication?
- For customers not using SSO, does your solution support local authentication protocols for user and administrator authentication?
- For customers not using SSO, can you enforce password/passphrase complexity requirements (provided by the institution)?
- For customers not using SSO, does the system have password complexity or length limitations and/or restrictions?
- For customers not using SSO, do you have documented password/passphrase reset procedures that are currently implemented in the system and/or customer support?
- Does your organization participate in InCommon or another eduGAIN-affiliated trust federation?
