Skip to main content
Every organization has an identity fabric — it’s the collection of identity providers, directories, and authentication systems that together determine who can access what. For most enterprises, this fabric is not a single system. It’s Entra ID for cloud apps, Active Directory for on-prem resources, an LDAP directory for legacy systems, maybe Okta or PingFederate from an acquisition. Different protocols, different vendors, different eras of technology — all serving the same fundamental purpose. The Maverics Orchestrator connects to your identity fabric through connectors. Each connector integrates with one identity provider or attribute source, abstracting the protocol details (OIDC, SAML, LDAP) behind a uniform interface. This means the Orchestrator can authenticate users against any provider, pull attributes from any directory, and translate between protocols — without your applications knowing or caring which systems are involved upstream.
Console terminology: In the Maverics Console, this section is called Identity Fabric. The YAML configuration uses the connectors key to define identity provider integrations.

Available Connectors

The Orchestrator ships with connectors for the identity providers and directories enterprises use most.
ConnectorProtocolUse Case
1Kosmos (SAML)SAML1Kosmos passwordless MFA
Amazon Cognito (OIDC)OIDCCognito user pool SSO, AWS identity
Auth0 (OIDC)OIDCAuth0 SSO federation, tenant migration
ContinuityFailover aggregationIdP failover, zero-downtime migration
Generic OIDCOIDCAny OIDC-compliant provider
Generic SAMLSAML 2.0Any SAML-compliant provider
CyberArk (OIDC)OIDCCyberArk Identity SSO
CyberArk (SAML)SAML 2.0CyberArk Identity SAML federation
Duo (SAML)SAML 2.0Duo Security MFA federation
Google Workspace (OIDC)OIDCGoogle Workspace SSO (uses generic OIDC)
HYPRHYPRHYPR passwordless authentication
Keycloak (OIDC)OIDCKeycloak SSO federation
LDAP AuthenticationLDAP/LDAPSLDAP bind authentication for end users
LDAP Attribute ProviderLDAP/LDAPSLDAP attribute lookups for enrichment
Microsoft Active DirectoryLDAP (via AD)Active Directory integration
Microsoft ADFS (SAML)SAML 2.0ADFS-to-cloud migration, hybrid federation
Microsoft Entra ID (OIDC)OIDCEntra ID SSO, hybrid identity
Microsoft Entra ID (SAML)SAML 2.0Entra ID SAML-based federation
Microsoft Entra ID Attribute ProviderGraph APIEntra ID attribute enrichment via Microsoft Graph
Microsoft Windows Client AuthenticatorWindows authWindows desktop credential authentication via IIS
Okta (OIDC)OIDCOkta SSO consolidation, legacy app bridging
Okta (SAML)SAML 2.0Okta SAML-based federation
Okta Attribute ProviderOkta APIOkta attribute enrichment via API
Oracle Identity Cloud Service (OIDC)OIDCOracle IDCS SSO
Oracle Universal Directory (LDAP)LDAP/LDAPSOracle OUD directory integration
PingFederate (OIDC)OIDCPingFederate on-premises federation
PingFederate (SAML)SAML 2.0PingFederate SAML-based federation
Trusona (OIDC)OIDCTrusona identity verification
WSO2 Identity Server (OIDC)OIDCWSO2 Identity Server SSO

Mode Compatibility

Identity Fabric connectors work with all five Orchestrator modes. The connector determines which protocol the Orchestrator uses to communicate with your identity provider. The mode determines which protocol the Orchestrator uses to communicate with your application. These are independent — an OIDC connector can feed a SAML Provider mode app, and a SAML connector can feed an OIDC Provider mode app. The Orchestrator handles all protocol translation.
  • OIDC connectors (Microsoft Entra ID, Okta, Auth0, PingFederate, Amazon Cognito, Generic OIDC) — Used with all modes. Most common for OIDC Provider and HTTP Proxy.
  • SAML connectors (Generic SAML, Microsoft ADFS, Entra ID SAML, Okta SAML, PingFederate SAML, CyberArk SAML, Duo) — Used primarily with SAML Provider and HTTP Proxy. The Orchestrator translates SAML upstream to any downstream protocol.
  • LDAP connectors (LDAP, Microsoft Active Directory, Oracle Universal Directory) — Used primarily as attribute providers (enriching claims with directory data). Most common with HTTP Proxy and LDAP Provider modes.
  • Continuity connector — Mode-agnostic. Wraps other connectors to provide IdP failover.
See the connector compatibility matrix for the full matrix showing which connectors are commonly paired with which modes.

Setup

To create an Identity Fabric connector in the Maverics Console:
  1. Navigate to Identity Fabric in the Console sidebar.
  2. Click Create to open the connector type selection dialog.
  3. Select the connector type that matches your identity provider (e.g., Microsoft Entra ID (OIDC), Okta (OIDC), Generic SAML).
  4. Fill in the required fields for your selected connector type — see the individual connector pages for field-by-field instructions.
  5. Click Save.
Each connector type has its own configuration form. See the individual connector pages linked below for detailed Console UI walkthroughs specific to each provider.

Connector Pages