# Single Sign On (SSO)

**Single Sign-On (SSO)** is an authentication method that allows users to log in once and gain access to multiple systems without re-entering credentials. By leveraging SSO, organizations can centralize user management, enhance security, and streamline the login experience.

LicenseSpring supports SSO integration to help vendors and end users access our platforms using their existing identity provider (IdP). This is especially useful for teams managing access at scale and seeking to enforce consistent security policies across applications.

LicenseSpring currently supports SSO for two interfaces:

{% stepper %}
{% step %}

### Vendor Platform SSO

The **Vendor Platform SSO** allows administrators and team members of software vendors to log into the LicenseSpring management dashboard using their organization’s identity provider. This integration supports SAML 2.0 and OIDC protocols, enabling seamless authentication via widely used IdPs such as Okta, Azure AD, Google Workspace, and others.

Vendor platform SSO provides centralized access control and is ideal for managing internal access to license data, product configurations, and customer records. Once configured, organization members can use their corporate credentials to sign in without needing a separate LicenseSpring account.
{% endstep %}

{% step %}

### User Portal SSO

The **User Portal SSO** enables LicenseSpring customers (software vendors) to offer a unified login experience for their end users and license managers via the hosted **User Portal**. This allows end users and license managers to access license details, activations, and self-service options using credentials from an external identity system.

User Portal SSO is commonly used when vendors have an existing user database or authentication flow and wish to avoid requiring separate login credentials for LicenseSpring-hosted services. The User Portal can be configured to accept authentication via the vendor’s IdP, using supported protocols such as SAML or OIDC. This functionality allows vendors to integrate their existing identity infrastructure—such as Google, Azure AD, Okta, Auth0, or any SAML/OIDC-compliant provider—into the user-facing authentication process.

This is particularly beneficial for:

* **Enterprise software** vendors distributing licensed applications across teams or departments
* **B2B SaaS platforms** requiring customer-level user management
* **ISVs** managing a customer base with centralized identity systems
  {% endstep %}
  {% endstepper %}

## Next Steps

* To set up SSO for either platform, refer to the respective integration guides:
  * [**Vendor Platform SSO**](https://docs.licensespring.com/common-scenarios/single-sign-on-sso/vendor-platform-sso)
  * [**User portal SSO**](https://docs.licensespring.com/common-scenarios/single-sign-on-sso/user-portal-sso)

{% hint style="info" %}
LicenseSpring now supports a **new IdP system**, migrating all existing SSO setups and appending the `"legacy-"` prefix.

If you are modifying an existing integration, it is **recommended to delete the old setup and configure a new one** following the updated documentation.

**Key Differences in SSO URLs:**

* User portal SSO (for licensing and user portals) uses **different URL values** from the vendor platform SSO.
* The `/api/v4/sso_url` endpoint should be used to generate login links dynamically.
  {% endhint %}

If you require assistance or have custom SSO requirements, please contact [**LicenseSpring Support**](https://licensespring.zendesk.com/agent/).


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.licensespring.com/common-scenarios/single-sign-on-sso.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.