# How do I connect self-hosted software to my identity provider?

Canonical page: https://launchinyourcloud.com/questions/identity-provider/

Check the exact edition’s SAML or OIDC support, configure the identity-provider connection, and test login and removal of access. Review API identities and SCIM provisioning separately. Browser SSO does not automatically secure every client or manage the full user lifecycle.

Answer page: https://launchinyourcloud.com/questions/identity-provider/
Answer reviewed: 2026-11-21

- [Browse deployment definitions](/glossary/#sso)
- [Distinguish SCIM provisioning](/glossary/#scim)
- [Filter for documented SSO evidence](/directory/?requires=sso)


## Confirm the supported connection

Check the protocol, product edition, deployment mode and client types covered by the documentation. Browser login, command-line clients, APIs and service accounts may use different credentials. Record redirect URLs, identity claims, role mappings and the administrator recovery procedure for the chosen integration.

## Test the complete access lifecycle

Create a test user, authenticate, change its group or role and remove access. Check existing sessions and API credentials as well as new logins. Document what your identity provider controls and what remains local to the application.

If automatic provisioning is required, review SCIM separately, including supported user and group operations and edition limits. First-login account creation alone does not establish provisioning or deactivation. Keep a tested emergency administrator procedure so an identity-provider problem does not prevent recovery of the application.

