Skip to main content

SSO Configuration

Overview: Single Sign-On (SSO) Configuration

What is SSO?​

Single Sign-On (SSO) is an authentication mechanism that allows users to log in once and gain access to multiple applications without needing to re-enter credentials. By integrating with SSO providers like Azure AD and Okta, APIsec enables secure, centralized user authentication and access management.

With SSO, organizations can:

  • Enhance Security – Reduces password-related vulnerabilities by enforcing centralized authentication policies.
  • Improve User Experience – Eliminates the need for multiple logins, streamlining access to APIsec.
  • Ensure Compliance – Meets enterprise security standards for authentication and access control.

Supported SSO Providers​

  • Azure AD (Microsoft Entra ID) – Enterprise identity management for Microsoft environments.
  • Okta – Cloud-based identity provider for authentication and access control.

SSO Configuration with APIsec​

To simplify integration with identity providers, APIsec offers a guided SSO setup with a streamlined workflow.

Step 1: Connect to Your SSO Provider​

  • Choose between Azure AD or Okta as the authentication provider.
  • Provide necessary configuration details such as SSO domain, client ID, and secret key.

Step 2: Configure User Roles & Access Control​

  • Map SSO user groups to APIsec RBAC roles (Admin, Developer, Viewer, etc.).
  • Define authentication policies and access restrictions.

Step 3: Enable & Test SSO Login​

  • Activate the SSO integration for your APIsec instance.
  • Verify authentication flow by logging in through the SSO provider.
  • Ensure users are mapped correctly and have appropriate permissions.

Benefits of SSO Integration​

  • Centralized Identity Management – Ensures all users authenticate through a trusted identity provider.
  • Reduced IT Overhead – Eliminates the need to manage separate credentials for APIsec.
  • Seamless User Experience – Enables faster, frictionless access across teams.