Skip to main content

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, Okta, and Ping Identity, APIsec enables secure, centralized user authentication and access management. Centralizing authentication reduces password-related vulnerabilities, removes separate logins for APIsec, and supports enterprise compliance requirements for 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.
  • Ping Identity – Enterprise identity platform for authentication and access control.

SSO Configuration with APIsec​

APIsec provides a guided SSO setup for integrating with your identity provider.

Step 1: Connect to Your SSO Provider​

  • Choose Azure AD, Okta, or Ping Identity as the authentication provider.
  • Provide your identity provider's SAML metadata URL. That is the only configuration detail APIsec needs.

Step 2: Configure User Roles & Access Control​

  • APIsec has four platform roles: Admin, User, Viewer, and Global Viewer. You do not map groups inside APIsec — assign each user to the APISEC_ADMIN, APISEC_USER, APISEC_VIEWER, or APISEC_GLOBAL_VIEWER group in your identity provider, and APIsec reads the role from the apisecroles claim at sign-in. A user in none of those groups signs in as User.

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.