> For the complete documentation index, see [llms.txt](https://docs.premsoft.de/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.premsoft.de/en/plugins/single-sign-on-sso.md).

# Single Sign On - SSO

### Introduction

The system supports Single Sign-On (SSO), meaning that users only need to authenticate once to access multiple services.

<figure><img src="/files/GUktStYvEjggIVU47wek" alt=""><figcaption></figcaption></figure>

Integrating Single Sign-On (SSO) into the Shopware 6 storefront provides customers with a more convenient and secure user experience. With SSO, users only need to authenticate once to access their customer account and other connected services without repeated logins. This reduces login barriers and improves conversion rates by enabling a seamless shopping experience.

Our Shopware 6 plugin supports established identity providers such as **Okta** and **Azure Active Directory**. Additionally, custom authentication services can be integrated as long as they support the **OAuth2 protocol**. This offers businesses high flexibility and allows them to seamlessly integrate existing security and user management systems.


---

# 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 dynamically by asking a question.

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

```
GET https://docs.premsoft.de/en/plugins/single-sign-on-sso.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.