> For the complete documentation index, see [llms.txt](https://docs.licensespring.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.licensespring.com/common-scenarios/single-sign-on-sso/frequently-asked-questions.md).

# Frequently Asked Questions

<details>

<summary><strong>Is there a way for Customer Account SSO to auto-create a LicenseSpring user on login?</strong></summary>

Not at the moment. Automatic user creation is **only available for platform users**.

</details>

<details>

<summary><strong>What does "Implemented Keycloak integration in all API endpoints" in v4.0.35 mean?</strong></summary>

The IdP system has changed, and all SSO setups have been migrated. If you see unexpected behavior, such as different authentication types being displayed (e.g., OIDC vs. SAML), please send the specific setups to support for verification.

</details>

<details>

<summary><strong>Is auth URL for identity providers the same on single tenancy accounts?</strong></summary>

No, for single tenancy accounts, auth url is provided by us instead of default one (`auth.licensespring.com`). This auth URL is used when registering your application in identity providers dashboard.

</details>


---

# 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.licensespring.com/common-scenarios/single-sign-on-sso/frequently-asked-questions.md?ask=<question>&goal=<user_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.