For customers not using SSO, does your application support directory integration for user accounts?

This question is asking whether your application can integrate with directory services (like Microsoft Active Directory, LDAP, etc.) for user account management when Single Sign-On (SSO) is not being used. Directory integration allows organizations to manage user accounts centrally in their existing directory service rather than maintaining separate user accounts in each application. This provides several benefits: 1. Centralized user management: When users join or leave an organization, their access can be granted or revoked in one place 2. Consistent password policies: The organization's password requirements are applied uniformly 3. Reduced administrative overhead: No need to manage separate user databases for each application 4. Better security: Faster deprovisioning of access when employees leave The security assessment is asking this because directory integration is considered a security best practice. Without it, organizations face challenges like: - Orphaned accounts when users leave the organization - Inconsistent password policies across applications - Manual user management processes that are error-prone - Difficulty maintaining compliance with access control requirements When answering this question, you should clearly state whether your application supports directory integration, which specific directory services you support (e.g., Microsoft Active Directory, Azure AD, LDAP, Okta, etc.), and briefly explain how the integration works.