SSO integrations
Configure single sign-on between SecureAuth Connect and a specific SaaS application. As an administrator, you create a standard SAML service provider or OIDC client on the SecureAuth side, then copy the matching values into the SSO settings on the application side. The guides below walk through the exact fields each application expects.
💡 Why this matters
Every SaaS application names and arranges its SSO fields differently. Vendor-specific guides save you the back-and-forth of figuring out which value goes where.
Vendor-specific guides​
- BambooHR – SAML SSO setup for BambooHR.
- Citrix StoreFront – SAML SSO setup for Citrix StoreFront.
Don't see your application?​
If your application isn't listed here, configure SSO yourself using the standard application types:
- Add a SAML service provider – most enterprise SaaS applications use SAML for SSO; this is the typical path.
- For applications that support OIDC-based SSO, see Applications overview to pick the right OAuth client type.
After you create the SecureAuth-side client, paste the metadata into the SSO settings on the application side using the field names the application expects.
Looking for identity providers instead?​
If you want to connect an IdP like Okta, Azure AD, or Google so users can sign in to SecureAuth Connect, see Identity providers.