General Protocol Setups
Single Sign-On (SSO) allows users to securely authenticate with multiple applications using a single set of credentials. This improves security, simplifies the user experience, and centralizes identity management. This guide provides setup instructions for integrating SSO with three common identity protocols: Active Directory/LDAP, OAuth 2.0, and SAML.
Each protocol supports different authentication flows and use cases. Depending on your organization's infrastructure and security requirements, you can choose the most suitable protocol or integrate multiple methods for flexibility.
Supported Protocols:
Active Directory/LDAP: Used to authenticate users against an existing on-premises directory service such as Microsoft Active Directory or OpenLDAP. Ideal for internal network environments.
OAuth 2.0: A modern authorization framework that allows third-party applications to access user data without exposing credentials. Commonly used for integrations with identity providers like Microsoft Entra ID (Azure AD), Google Workspace, and Okta.
SAML (Security Assertion Markup Language): An XML-based protocol used for exchanging authentication and authorization data between an identity provider (IdP) and a service provider (SP). Common in enterprise environments for web-based SSO.
What You'll Find in Each Setup Guide:
Prerequisites: Information you’ll need in advance (e.g., admin access, certificates, endpoints).
Configuration Steps: Step-by-step instructions to set up the connection between your identity provider and the platform.
Testing & Troubleshooting: Guidance on validating the setup and resolving common issues.
Security Tips: Best practices for securing your SSO configuration.
Follow the guide for the specific protocol you plan to use. If you're unsure which one is right for your organization, consult with your IT or security team.
Last updated