For business
Add Harbor SSO
Standards-based OIDC/OAuth 2.1 with PKCE, plus a SAML bridge for legacy stacks. Give customers passkey sign-in as a relying party without building identity infrastructure yourself.
OIDC / OAuth 2.1 with PKCE
Connect as a standard OpenID Connect relying party using the authorization code flow with PKCE. If your stack already speaks OIDC, most of the integration is configuration, not new code.
SAML bridge for legacy stacks
Applications that only speak SAML can integrate through the SAML bridge (enterprise/saml-bridge), which fronts Harbor's OIDC provider with a standard SAML 2.0 service-provider interface.
Pairwise identifiers, not a shared login
Your relying party receives its own pairwise identifier for each user — not an identifier shared across other relying parties — so your integration doesn't depend on cross-site correlation.
Integration effort and what’s on you
Harbor Cloud provides the standards-based identity provider and the SAML bridge. Integrating it, running your trial, and operating your side of the connection are your responsibility — this isn’t a fully managed migration.
- Registering your application as a relying party and configuring redirect URIs, scopes, and claims mapping for your environment.
- Running your own trial/pilot and validating the integration against your authentication and authorization requirements before production traffic.
- Ongoing operational tasks on your side of the integration: session handling in your application, your own uptime and monitoring, and rotating your client credentials.
Ready to add Harbor SSO?
See the full integration guide or read the developer docs for OIDC/OAuth 2.1 endpoint and SAML bridge details.