> For the complete documentation index, see [llms.txt](https://docs.flosum.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.flosum.com/global-settings/security/identity-providers-sso/overview-of-identity-provider-sso.md).
# Overview of Identity Provider (SSO)
##  Overview
Flosum Cloud Apps provides secure, centralized access control by supporting Single Sign-On (SSO) for its applications. This feature allows users to log in with their corporate credentials, providing a seamless, secure login experience.
{% hint style="info" %}
Flosum Cloud Apps supports SSO from an identity provider using either of the following protocols:
* OIDC (OpenID Connect)
* SAML (Security Assertion Markup Language)
{% endhint %}
To enable SSO, you need to integrate an identity provider with Flosum Cloud Apps through the Global Settings app. If your organization uses different identity providers for testing and production, you can configure multiple providers.
## Logging In With SSO
When an identity provider is added to your Flosum tenant, a custom SSO button will appear on the login screen. This button redirects users to the identity provider's login page. After they authenticate, they're returned to the Flosum app. For SSO login instructions, see the following article.
* [Logging In With SSO](/global-settings/security/identity-providers-sso/logging-in-with-sso.md)
{% hint style="warning" %}
If the SSO button you created with the Identity Provider is missing from the tenant login screen, there may be an issue with the provider details. Verify that the Identity Provider configuration matches the SSO credentials.
{% endhint %}
## Add an Identity Provider
For general instructions for adding an identity provider to your tenant in Global Settings, see the following article.
* [Adding an Identity Provider (SSO)](/global-settings/security/identity-providers-sso/adding-an-identity-provider-sso.md)
The following articles give provider-specific instructions and details for integrating your tenant with the most common identity providers.
**OIDC**
* [Auth0 - OIDC - Configuration](/global-settings/security/identity-providers-sso/oidc-identity-providers/auth0-oidc-configuration.md)
* [AWS Cognito - OIDC - Configuration](/global-settings/security/identity-providers-sso/oidc-identity-providers/aws-cognito-oidc-configuration.md)
* [Microsoft Entra ID - OIDC - Configuration](/global-settings/security/identity-providers-sso/oidc-identity-providers/microsoft-entra-id-oidc-configuration.md)
* [Google IDP - OIDC - Configuration](/global-settings/security/identity-providers-sso/oidc-identity-providers/google-idp-oidc-configuration.md)
**SAML**
* [Microsoft Entra ID - SAML - Configuration](/global-settings/security/identity-providers-sso/saml-identity-providers/microsoft-entra-id-saml-configuration.md)
* [Okta - SAML - Configuration](/global-settings/security/identity-providers-sso/saml-identity-providers/okta-saml-configuration.md)
## Just-In-Time Provisioning
Flosum supports Just-In-Time (JIT) Provisioning for both OIDC and SAML identity providers. JIT Provisioning automatically creates and updates user accounts in Global Settings when a user first logs in via SSO. Since the identity provider supplies user information, JIT Provisioning saves time by eliminating the need to manually create users. Your identity provider must be properly configured before you enable JIT Provisioning. See the following article to learn more about JIT Provisioning and how to configure your identity provider.
* [Configuring Just-In-Time (JIT) Provisioning](/global-settings/security/identity-providers-sso/configuring-just-in-time-jit-provisioning.md)
## SCIM Support
Flosum supports System for Cross-domain Identity Management (SCIM). SCIM lets you provision, manage, and deprovision users in your Flosum tenant through Flosum's SCIM API. To learn more about using SCIM with your tenant, see the following article.
* [Configuring SCIM for Flosum](/global-settings/security/identity-providers-sso/configuring-scim-for-flosum.md)
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.flosum.com/global-settings/security/identity-providers-sso/overview-of-identity-provider-sso.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
