---
title: "Introduction"
manual: "SSO Auth"
version: "main"
permalink: "https://docs.typo3.org/permalink/davitec/dv-sso-auth:introduction@main"
source: "Introduction/Index.rst"
rendered: "2026-10-12T13:45:55+00:00"
---

# Introduction {#introduction}

**On this page**

-   [What does it do?](https://docs.typo3.org/permalink/davitec/dv-sso-auth:what-does-it-do@main)
-   [Features](https://docs.typo3.org/permalink/davitec/dv-sso-auth:features@main)
-   [How SSO requests are detected](https://docs.typo3.org/permalink/davitec/dv-sso-auth:how-sso-requests-are-detected@main)
-   [Compatibility](https://docs.typo3.org/permalink/davitec/dv-sso-auth:compatibility@main)

## What does it do? {#what-does-it-do}

**SSO Auth** integrates Shibboleth-based single sign-on (SSO) into TYPO3.
It provides a dedicated TYPO3 authentication service and optional user
provisioning for frontend and backend accounts.

## Features {#features}

-   SSO authentication service for TYPO3 frontend and backend login
-   Dedicated backend login provider with an SSO button
-   Frontend login plugin with SSO login and logout flow
-   Optional auto-import and update of FE users from IdP attributes
-   Optional auto-import and update of BE users from IdP attributes
-   FE and BE group mapping based on affiliation attributes
-   Frontend middleware to recover from stale FE session cookies during SSO
-   Hook extension points for custom group assignment and `onlySsoBE` handling

## How SSO requests are detected {#how-sso-requests-are-detected}

The extension treats a request as SSO-related when one of these conditions
is true:

-   `AUTH_TYPE=shibboleth` (case-insensitive)
-   `Shib_Session_ID` exists
-   `REDIRECT_Shib_Session_ID` exists
-   `Shib-Session-ID` exists
-   `REDIRECT_Shib-Session-ID` exists

This logic is implemented in `SsoRequestDetector`.

## Compatibility {#compatibility}

According to `composer.json` the extension supports:

-   TYPO3 `^12.4 || ^13.4`
-   PHP `^8.1 || ^8.2 || ^8.3 || ^8.4 || ^8.5`