Enterprise Connections

Let your customers sign in with their own identity provider — SAML 2.0 and Active Directory / LDAP, unlimited and free

Enterprise SSO

The Feature That Closes Enterprise Deals

Every enterprise buyer eventually asks the same question: can our employees sign in with our existing identity provider? Without SSO, the answer stalls the deal. With it, your application slots into the customer's existing access controls, offboarding, and audit processes.

AuthAction supports SAML 2.0 and Active Directory / LDAP, with step-by-step guides for the identity providers enterprises actually use. Connections are configured per tenant, so each of your customers can bring their own provider.

Request Demo View Documentation API Reference

Why Enterprise SSO?

What your customers' IT teams need before they can approve your application

Centralised Access

Employees sign in with the corporate account they already have. No extra password to create, forget, or reuse, and no separate credential store for IT to worry about.

Instant Offboarding

When someone leaves, disabling their account in the identity provider removes access to your application too. That single property is often what security review is really asking about.

Unlimited, Not Upsold

Enterprise SSO is commonly gated behind the most expensive tier. On AuthAction it is included at no cost, with no cap on the number of connections.

Supported Providers

Guided setup for the identity providers enterprises actually run

Okta Workforce

Connect an Okta SAML application to your tenant, with attribute mapping for email, name, and group membership.

Setup guide

Microsoft Entra ID

SAML single sign-on with Microsoft Entra ID (formerly Azure Active Directory), the most common enterprise directory.

Setup guide

Google Workspace

Configure Google Workspace as a SAML identity provider so staff sign in with their managed Google account.

Setup guide

ADFS

Active Directory Federation Services, for customers running their own on-premises federation infrastructure.

Setup guide

PingFederate

Federate with PingFederate deployments, common in financial services and other regulated industries.

Setup guide

JumpCloud

Connect JumpCloud's cloud directory, frequently used by smaller and mid-sized organisations without on-premises AD.

Setup guide

Generic SAML 2.0

Any SAML 2.0 identity provider works, whether or not it has a dedicated guide. Supply the entry point, issuer, and signing certificate and the connection is ready.

  • Signed AuthnRequests
  • X.509 certificate validation
  • Attribute mapping
Setup guide

Active Directory / LDAP

Authenticate directly against an LDAP directory for customers who have not federated. Bind credentials, base DN, and search filter are configured per connection.

  • LDAPS supported
  • Custom search filters
  • Configurable base DN
Setup guide

How It Works

Add an enterprise connection in three steps

1

Create the Connection

In the AuthAction Dashboard, go to Connections → Enterprise Connections and choose your customer's identity provider.

2

Exchange Metadata

Paste the identity provider's entry point, issuer, and signing certificate, and register AuthAction's callback URL on their side.

3

Enable and Test

Enable the connection for your application and sign in. Your application receives standard OIDC tokens — no SAML handling in your own code.

Your application always speaks OIDC, whatever the customer runs 

SAML / LDAP                 OIDC
─────────────               ─────────────
Okta          ─┐
Entra ID       │
Google         ├──>  AuthAction  ──>  Your application
ADFS           │                       (id_token + access_token)
PingFederate   │
JumpCloud     ─┘
AD / LDAP     ─┘

AuthAction terminates SAML and LDAP so your application only ever implements OpenID Connect.

Frequently Asked Questions

Common questions about Enterprise Connections

Yes. Enterprise connections are unlimited and included at no cost, like every other AuthAction feature. There is no enterprise tier to upgrade to and no per-connection charge.

No. AuthAction handles the SAML or LDAP exchange and issues standard OpenID Connect tokens to your application. Your integration code is the same whether the user signed in with a password, a social provider, or their corporate identity provider.

Use the generic SAML 2.0 connection. The named providers have dedicated guides because they are the most common, but any standards-compliant SAML 2.0 identity provider can be configured with its entry point, issuer, and signing certificate.

Yes. Connections are configured per tenant, and a tenant can have multiple enterprise connections at once. One customer can sign in through Okta while another uses Entra ID and a third authenticates against LDAP.

Further reading

From the blog

All posts

In the docs

Full documentation

Ready to say yes to enterprise SSO?

Add unlimited SAML and LDAP connections to your application and stop losing deals to a security questionnaire. Completely free, no credit card required.

Get Started View Pricing