SAML Single Sign On SSO (Backend + Frontend)

Classification

miniorange-saml

Version

main

Language

en

Description

SAML Single Sign On SSO (Backend + Frontend)

Keywords

saml sso, sso, single sign on, single sign-on, Azure AD, Okta, Google SSO, frontend, backend, login

Copyright

2021

Author

miniOrange

Email

info@xecurify.com

License

This document is published under the Open Content License available from http://www.opencontent.org/opl.shtml

Rendered

Tue, 16 Sep 2025 11:13:19 +0000

The content of this document is related to TYPO3, a GNU/GPL CMS/Framework available from www.typo3.org.

Table of Contents

Installation

Extension Installation

Using composer:

Use the below command to install the extension using composer:

composer req miniorange/miniorange-saml
Copied!

OR

Using zip file:

  • Download the zip file of the miniOrange SAML SSO extension from TYPO3 marketplace.
  • Rename the zip file from miniorange_saml.zip to sp.zip
  • Go to your TYPO3 backend and click on Extensions section at the left side of your screen.
  • Upload the zip file as represented in the below image.
Upload Extension zip

SP-Configurations

Pre-requirements Before Configuring SP-Configurations

You must have atleast two pages before configuring the extension.

  • Navigate to the Pages section and create new standard page with name fesaml and add fesaml plugin to it.
  • Similarly create a page named response and and response plugin to it.
  • You can refer to the below screenshots for the same.
Response Page * Create SSO Login button in your Typo3 Frontend Site and embed the fesaml page URL to it in order to initiate the SSO.

Service Provider Metadata Configurations

  • Once the extension is installed successfully, navigate to the SP settings tab and configure the fields as below:
- Fesaml plugin page URL: {URL of the Fesaml standard page created in earlier steps}
  • Response plugin page URL: {URL of the Response standard page created in earlier steps}
  • Base URL: {Base URL of your Typo3 site}
  • ACS URL: {URL of the Response standard page created in earlier steps}
  • Issuer/Entity ID: {Base URL of your Typo3 site}
Service Provider Configurations
  • Once you save the above details, you can download the SP XML Metadata or you can use XML Metadata URL to upload it in your Identity Provider or you can upload it manually.
  • You can choose the setup guide specific to your Identity Provider from below link:

https://plugins.miniorange.com/typo3-saml-sso-setup-guides

IDP-Configurations

Identity Provider Metadata Configurations (Using XML Metadata)

  • Either download the IDP Metadata file or copy the IDP Metadata URL from your Identity Provider
  • Navigate to the IDP Settings tab of the plugin and click on Upload IDP Metadata button
  • Add the name of your Identity Provider.
  • add the downloaded IDP Metadata file or paste the IDP Metadata URL copied from your Identity Provider and save it.
IDP XML Metadata Upload
  • Once you save the settings all the Metadata details will be fetched automatically.

OR

Identity Provider Metadata Configurations (Manually)

  • Identity Provider Name: {Add your Identity Provider Name}
  • IDP Entity ID: {Add your Identity Provider Entity ID}
  • SAML Login URL: {Add your Identity Provider Single Sign On Service URL}
  • SAML x509 Certificate: {Add your Identity Provider x509 certificate}
Identity Provider Configurations
  • Once you configure both Identity Provider and Service Provider Metadata, click the Test Configuration button to check if the configurations are made correctly.
Test Configuration Window

Default Group Mapping

  • Navigate to the Group Mapping tab of the plugin, select the default group to be assigned to the new users in Typo3 and save the settings.
Group Mapping Settings
  • Once you have done all the above steps, you are ready to test the SSO. You can use your Fesaml Page URL in order to initiate the SSO.
  • If you are looking for anything which you cannot find, please drop us an email on info@xecurify.com

Administrator Manual

Target group: Administrators

Describes how to manage the extension from an administrator point of view. That relates to Page/User TSconfig, permissions, configuration etc., which administrator level users have access to.

Language should be non / semi-technical, explaining, using small examples.

Installation

  • How should the extension be installed?
  • Are they dependencies to resolve?
  • Is it a static template file to be included?

To install the extension, perform the following steps:

  1. Go to the Extension Manager
  2. Install the extension
  3. Load the static template
  4. ...

For a list of configuration options, using a definition list is recommended:

Some Configuration
This option enables...
Other configuration
This other option is for all the rest...
Extension Manager

Extension Manager (caption of the image)

List of extensions within the Extension Manager also shorten with "EM" (legend of the image)

Configuration

  • Where and how the extension should be configured? TypoScript? PHP?
  • Are there other prerequisite to full fill beforehand? For example, configure a setting in a special way somewhere.

FAQ

Possible subsection: FAQ

Subsection

Some subsection

Sub-subsection

Deeper into the structure...

ChangeLog

Providing a change log chapter is optional. You can also refer users to the ChangeLog file inside the extension or to some repository's commit listing.

Introduction

What does it do?

This chapter should give a brief overview of the extension. What does it do? What problems does it solve? Who is interested in this? Basically, this section includes everything people need to know to decide whether they should go on with this extension or not.

Screenshots

This chapter should help people figure how the extension works. Remove it if not relevant.

Introduction Package

Introduction Package just after installation (caption of the image)

How the Frontend of the Introduction Package looks like just after installation (legend of the image)