Download the PHP package patrickallaert/php-saml without Composer

Patrick Allaert's SAML PHP Toolkit Compatible with PHP 7.1+ based on OneLogin's

Add SAML support to your PHP software using this library.

Warning

This version is compatible with PHP 7.1+ and does not include xmlseclibs (you will need to install it via composer, dependency described in composer.json)

Why add SAML support to my software?

SAML is an XML-based standard for web browser single sign-on and is defined by the OASIS Security Services Technical Committee. The standard has been around since 2002, but lately it is becoming popular due its advantages:

• Usability - One-click access from portals or intranets, deep linking, password elimination and automatically renewing sessions make life easier for the user.
• Security - Based on strong digital signatures for authentication and integrity, SAML is a secure single sign-on protocol that the largest and most security conscious enterprises in the world rely on.
• Speed - SAML is fast. One browser redirect is all it takes to securely sign a user into an application.
• Phishing Prevention - If you don’t have a password for an app, you can’t be tricked into entering it on a fake login page.
• IT Friendly - SAML simplifies life for IT because it centralizes authentication, provides greater visibility and makes directory integration easier.
• Opportunity - B2B cloud vendor should support SAML to facilitate the integration of their product.

General description

SAML PHP toolkit let you build a SP (Service Provider) over your PHP application and connect it to any IdP (Identity Provider).

Supports:

• SSO and SLO (SP-Initiated and IdP-Initiated).
• Assertion and nameId encryption.
• Assertion signature.
• Message signature: AuthNRequest, LogoutRequest, LogoutResponses.
• Enable an Assertion Consumer Service endpoint.
• Enable a Single Logout Service endpoint.
• Publish the SP metadata (which can be signed).

Key features:

• saml2int - Implements the SAML 2.0 Web Browser SSO Profile.
• Session-less - Forget those common conflicts between the SP and the final app, the toolkit delegate session in the final app.
• Easy to use - Programmer will be allowed to code high-level and low-level programming, 2 easy to use APIs are available.
• Tested - Thoroughly tested.
• Popular - Many PHP SAML plugins uses it.

Installation

Dependencies

• php >= 7.1 and some core extensions like php-xml, php-date, php-zlib.
• openssl. Install the openssl library. It handles x509 certificates.
• gettext. Install that library and its php driver. It handles translations.
• curl. Install that library and its php driver if you plan to use the IdP Metadata parser.

Code

Option 1. Download from github

The toolkit is hosted on github. You can download it from:

• https://github.com/patrickallaert/php-saml/releases

Option 2. Composer

The toolkit supports composer. You can find the patrickallaert/php-saml package at https://packagist.org/packages/patrickallaert/php-saml

In order to import the saml toolkit to your current php project, execute

Important In this option, the x509 certs must be stored at vendor/patrickallaert/php-saml/certs and settings file stored at vendor/patrickallaert/php-saml.

Your settings are at risk of being deleted when updating packages using composer update or similar commands. So it is highly recommended that instead of using settings files, you pass the settings as an array directly to the constructor (explained later in this document). If you do not use this approach your settings are at risk of being deleted when updating packages using composer update or similar commands.

Security warning

In production, the strict parameter MUST be set as "true" and the signatureAlgorithm and digestAlgorithm under security must be set to something other than SHA1 (see https://shattered.io/ ). Otherwise your environment is not secure and will be exposed to attacks.

In production also we highly recommended to register on the settings the IdP certificate instead of using the fingerprint method. The fingerprint, is a hash, so at the end is open to a collision attack that can end on a signature validation bypass. Other SAML toolkits deprecated that mechanism, we maintain it for compatibility and also to be used on test environment.

Getting started

Knowing the toolkit

The SAML Toolkit contains different folders (certs, endpoints, lib, demo, etc.) and some files.

Let's start describing the folders:

certs/

SAML requires a x509 cert to sign and encrypt elements like NameID, Message, Assertion, Metadata.

If our environment requires sign or encrypt support, this folder may contain the x509 cert and the private key that the SP will use:

• sp.crt - The public cert of the SP
• sp.key - The private key of the SP

Or also we can provide those data in the setting file at the $settings['sp']['x509cert'] and the $settings['sp']['privateKey'].

Sometimes we could need a signature on the metadata published by the SP, in this case we could use the x509 cert previously mentioned or use a new x.509 cert: metadata.crt and metadata.key.

Use sp_new.crt if you are in a key rollover process and you want to publish that x509 certificate on Service Provider metadata.

src/

This folder contains the heart of the toolkit, the libraries:

• Saml2 folder contains the new version of the classes and methods that are described in a later section.

doc/

This folder contains the API documentation of the toolkit.

endpoints/

The toolkit has three endpoints:

• metadata.php - Where the metadata of the SP is published.
• acs.php - Assertion Consumer Service. Processes the SAML Responses.
• sls.php - Single Logout Service. Processes Logout Requests and Logout Responses.

You can use the files provided by the toolkit or create your own endpoints files when adding SAML support to your applications. Take in mind that those endpoints files uses the setting file of the toolkit's base folder.

locale/

Locale folder contains some translations: en_US and es_ES as a proof of concept. Currently there are no translations but we will eventually localize the messages and support multiple languages.

Other important files

• settings_example.php - A template to be used in order to create a settings.php file which contains the basic configuration info of the toolkit.
• advanced_settings_example.php - A template to be used in order to create a advanced_settings.php file which contains extra configuration info related to the security, the contact person, and the organization associated to the SP.

Miscellaneous

• tests/ - Contains the unit test of the toolkit.
• demo1/ - Contains an example of a simple PHP app with SAML support. Read the Readme.txt inside for more info.
• demo2/ - Contains another example.

How it works

Settings

First of all we need to configure the toolkit. The SP's info, the IdP's info, and in some cases, configure advanced security issues like signatures and encryption.

There are two ways to provide the settings information:

• Use a settings.php file that we should locate at the base folder of the toolkit.
• Use an array with the setting data and provide it directly to the constructor of the class.

There is a template file, settings_example.php, so you can make a copy of this file, rename and edit it.

In addition to the required settings data (IdP, SP), there is extra information that could be defined. In the same way that a template exists for the basic info, there is a template for that advanced info located at the base folder of the toolkit and named advanced_settings_example.php that you can copy and rename it as advanced_settings.php

The compression settings allow you to instruct whether or not the IdP can accept data that has been compressed using gzip ('requests' and 'responses'). But if we provide a $deflate boolean parameter to the getRequest or getResponse method it will have priority over the compression settings.

In the security section, you can set the way that the SP will handle the messages and assertions. Contact the admin of the IdP and ask him what the IdP expects, and decide what validations will handle the SP and what requirements the SP will have and communicate them to the IdP's admin too.

Once we know what kind of data could be configured, let's talk about the way settings are handled within the toolkit.

The settings files described (settings.php and advanced_settings.php) are loaded by the toolkit if no other array with settings info is provided in the constructor of the toolkit. Let's see some examples.

You can declare the $settingsInfo in the file that contains the constructor execution or locate them in any file and load the file in order to get the array available as we see in the following example:

How load the library

Use composer's vendor/autoload.php script if you used composer to install this library.

Otherwise, use a PSR-4 capable loader mechanism, knowing that namespace Saml2\ should be matched against the src/Saml2 folder.

Initiate SSO

In order to send an AuthNRequest to the IdP:

The AuthNRequest will be sent signed or unsigned based on the security info of the advanced_settings.php ('authnRequestsSigned').

The IdP will then return the SAML Response to the user's client. The client is then forwarded to the Attribute Consumer Service of the SP with this information. If we do not set a 'url' param in the login method and we are using the default ACS provided by the toolkit (endpoints/acs.php), then the ACS endpoint will redirect the user to the file that launched the SSO request.

We can set a 'returnTo' url to change the workflow and redirect the user to the other PHP file.

The login method can receive other five optional parameters:

• $parameters - An array of parameters that will be added to the GET in the HTTP-Redirect.
• $forceAuthn - When true the AuthNRequest will set the ForceAuthn='true'
• $isPassive - When true the AuthNRequest will set the Ispassive='true'
• $strict - True if we want to stay (returns the url string) False to redirect
• $setNameIdPolicy - When true the AuthNRequest will set a nameIdPolicy element.

If a match on the future SAMLResponse ID and the AuthNRequest ID to be sent is required, that AuthNRequest ID must to be extracted and saved.

The SP Endpoints

Related to the SP there are three important views: The metadata view, the ACS view and the SLS view. The toolkit provides examples of those views in the endpoints directory.

SP Metadata endpoints/metadata.php

This code will provide the XML metadata file of our SP, based on the info that we provided in the settings files.

The getSPMetadata will return the metadata signed or not based on the security info of the advanced_settings.php ('signMetadata').

Before the XML metadata is exposed, a check takes place to ensure that the info to be provided is valid.

Instead of use the Auth object, you can directly use

to get the settings object and with the true parameter we will avoid the IdP Settings validation.

Attribute Consumer Service(ACS) endpoints/acs.php

This code handles the SAML response that the IdP forwards to the SP through the user's client.

The SAML response is processed and then checked that there are no errors. It also verifies that the user is authenticated and stored the userdata in session.

At that point there are two possible alternatives:

1. If no RelayState is provided, we could show the user data in this view or however we wanted.

2. If RelayState is provided, a redirection takes place.

Notice that we saved the user data in the session before the redirection to have the user data available at the RelayState view.

The getAttributes method

In order to retrieve attributes we can use:

With this method we get all the user data provided by the IdP in the Assertion of the SAML Response.

If we execute we could get:

Each attribute name can be used as an index into $attributes to obtain the value. Every attribute value is an array - a single-valued attribute is an array of a single element.

The following code is equivalent:

Before trying to get an attribute, check that the user is authenticated. If the user isn't authenticated or if there were no attributes in the SAML assertion, an empty array will be returned. For example, if we call to getAttributes before a $auth->processResponse, the getAttributes() will return an empty array.

Single Logout Service (SLS) endpoints/sls.php

This code handles the Logout Request and the Logout Responses.

If the SLS endpoints receives a Logout Response, the response is validated and the session could be closed

If the SLS endpoints receives an Logout Request, the request is validated, the session is closed and a Logout Response is sent to the SLS endpoint of the IdP.

If you aren't using the default PHP session, or otherwise need a manual way to destroy the session, you can pass a callback method to the processSLO method as the fourth parameter

If we don't want that processSLO to destroy the session, pass a true parameter to the processSLO method

Initiate SLO

In order to send a Logout Request to the IdP:

Also there are eight optional parameters that can be set:

• $returnTo - The target URL the user should be returned to after logout.
• $parameters - Extra parameters to be added to the GET.
• $name_id - That will be used to build the LogoutRequest. If name_id parameter is not set and the auth object processed a SAML Response with a NameId, then this NameId will be used.
• $session_index - SessionIndex that identifies the session of the user.
• $stay - True if we want to stay (returns the url string) False to redirect.
• $nameIdFormat - The NameID Format will be set in the LogoutRequest.
• $nameIdNameQualifier - The NameID NameQualifier will be set in the LogoutRequest.
• $nameIdSPNameQualifier - The NameID SP NameQualifier will be set in the LogoutRequest.

The Logout Request will be sent signed or unsigned based on the security info of the advanced_settings.php ('logoutRequestSigned').

The IdP will return the Logout Response through the user's client to the Single Logout Service of the SP. If we do not set a 'url' param in the logout method and are using the default SLS provided by the toolkit (endpoints/sls.php), then the SLS endpoint will redirect the user to the file that launched the SLO request.

We can set an 'returnTo' url to change the workflow and redirect the user to other php file.

A more complex logout with all the parameters:

If a match on the future LogoutResponse ID and the LogoutRequest ID to be sent is required, that LogoutRequest ID must to be extracted and stored.

Example of a view that initiates the SSO request and handles the response (is the acs target)

We can code a unique file that initiates the SSO process, handle the response, get the attributes, initiate the SLO and processes the logout response.

Note: Review the demo1 folder that contains that use case; in a later section we explain the demo1 use case further in detail.

URL-guessing methods

php-saml toolkit uses a bunch of methods in Saml2\Utils that try to guess the URL where the SAML messages are processed.

• getSelfHost Returns the current host.
• getSelfPort Return the port number used for the request
• isHTTPS Checks if the protocol is https or http.
• getSelfURLhost Returns the protocol + the current host + the port (if different than common ports).
• getSelfURL Returns the URL of the current host + current view + query.
• getSelfURLNoQuery Returns the URL of the current host + current view.
• getSelfRoutedURLNoQuery Returns the routed URL of the current host + current view.

getSelfURLNoQuery and getSelfRoutedURLNoQuery are used to calculate the currentURL in order to valdate SAML elements like Destination or Recipient.

When the PHP application is behind a proxy or a load balancer we can execute setProxyVars(true) and setSelfPort and isHTTPS will take care of the $_SERVER["HTTP_X_FORWARDED_PORT"] and $_SERVER['HTTP_X_FORWARDED_PROTO'] vars (otherwise they are ignored).

Also a developer can use setSelfProtocol, setSelfHost, setSelfPort and getBaseURLPath to define a specific value to be returned by isHTTPS, getSelfHost, getSelfPort and getBaseURLPath. And define a setBasePath to be used on the getSelfURL and getSelfRoutedURLNoQuery to replace the data extracted from $_SERVER["REQUEST_URI"].

At the settings the developer will be able to set a 'baseurl' parameter that automatically will use setBaseURL to set values for setSelfProtocol, setSelfHost, setSelfPort and setBaseURLPath.

Working behind load balancer

Is possible that asserting request URL and Destination attribute of SAML response fails when working behind load balancer with SSL offload.

You should be able to workaround this by configuring your server so that it is aware of the proxy and returns the original url when requested.

Or by using the method described on the previous section.

SP Key rollover

If you plan to update the SP x509cert and privateKey you can define the new x509cert as $settings['sp']['x509certNew'] and it will be published on the SP metadata so Identity Providers can read them and get ready for rollover.

IdP with multiple certificates

In some scenarios the IdP uses different certificates for signing/encryption, or is under key rollover phase and more than one certificate is published on IdP metadata.

In order to handle that the toolkit offers the $settings['idp']['x509certMulti'] parameter.

When that parameter is used, 'x509cert' and 'certFingerprint' values will be ignored by the toolkit.

The x509certMulti is an array with 2 keys:

• signing. An array of certs that will be used to validate IdP signature
• encryption An array with one unique cert that will be used to encrypt data to be sent to the IdP

Replay attacks

In order to avoid replay attacks, you can store the ID of the SAML messages already processed, to avoid processing them twice. Since the Messages expires and will be invalidated due that fact, you don't need to store those IDs longer than the time frame that you currently accepting.

Get the ID of the last processed message/assertion with the getLastMessageId/getLastAssertionId methods of the Auth object.

Main classes and methods

Described below are the main classes and methods that can be invoked.

Saml2 library

Lets describe now the classes and methods of the SAML2 library.

Saml2\Auth - Auth.php

Main class of PHP Toolkit

• Auth - Initializes the SP SAML instance
• login - Initiates the SSO process.
• logout - Initiates the SLO process.
• processResponse - Process the SAML Response sent by the IdP.
• processSLO - Process the SAML Logout Response / Logout Request sent by the IdP.
• redirectTo - Redirects the user to the url past by parameter or to the url that we defined in our SSO Request.
• isAuthenticated - Checks if the user is authenticated or not.
• getAttributes - Returns the set of SAML attributes.
• getAttribute - Returns the requested SAML attribute
• getNameId - Returns the nameID
• getNameIdFormat - Gets the NameID Format provided by the SAML response from the IdP.
• getNameIdNameQualifier - Gets the NameID NameQualifier provided from the SAML Response String.
• getNameIdNameSPQualifier - Gets the NameID SP NameQualifier provided from the SAML Response String.
• getSessionIndex - Gets the SessionIndex from the AuthnStatement.
• getErrors - Returns if there were any error
• getLastRequestID - The ID of the last Request SAML message generated.
• buildRequestSignature - Generates the Signature for a SAML Request
• buildResponseSignature - Generates the Signature for a SAML Response
• getSettings - Returns the settings info
• setStrict - Set the strict mode active/disable
• getLastRequestID - Gets the ID of the last AuthNRequest or LogoutRequest generated by the Service Provider.

Saml2\AuthnRequest - AuthnRequest.php

SAML 2 Authentication Request class

• AuthnRequest - Constructs the AuthnRequest object.
• getRequest - Returns deflated, base64 encoded, unsigned AuthnRequest.
• getId - Returns the AuthNRequest ID.

Saml2\Response - Response.php

SAML 2 Authentication Response class

• Response - Constructs the SAML Response object.
• isValid - Determines if the SAML Response is valid using the certificate.
• checkStatus - Checks if the Status is success.
• getAudiences - Gets the audiences.
• getIssuers - Gets the Issuers (from Response and Assertion)
• getNameIdData - Gets the NameID Data provided by the SAML response from the IdP.
• getNameId - Gets the NameID provided by the SAML response from the IdP.
• getNameIdFormat - Gets the NameID Format provided by the SAML response from the IdP.
• getNameIdNameQualifier - Gets the NameID NameQualifier provided from the SAML Response String.
• getNameIdNameSPQualifier - Gets the NameID SP NameQualifier provided from the SAML Response String.
• getSessionNotOnOrAfter - Gets the SessionNotOnOrAfter from the AuthnStatement
• getSessionIndex - Gets the SessionIndex from the AuthnStatement.
• getAttributes - Gets the Attributes from the AttributeStatement element.
• validateNumAssertions - Verifies that the document only contains a single Assertion (encrypted or not).
• validateTimestamps - Verifies that the document is still valid according Conditions Element.
• getErrorException - After executing a validation process, if it fails, this method returns the exception triggered.

Saml2\LogoutRequest - LogoutRequest.php

SAML 2 Logout Request class

• LogoutRequest - Constructs the Logout Request object.
• getRequest - Returns the Logout Request defated, base64encoded, unsigned
• getID - Returns the ID of the Logout Request. (If you have the object you can access to the id attribute)
• getNameIdData - Gets the NameID Data of the the Logout Request.
• getNameId - Gets the NameID of the Logout Request.
• getIssuer - Gets the Issuer of the Logout Request.
• getSessionIndexes - Gets the SessionIndexes from the Logout Request.
• isValid - Checks if the Logout Request received is valid.
• getErrorException - After executing a validation process, if it fails, this method returns the exception triggered.
• getXML - Returns the XML that will be sent as part of the request or that was received at the SP.

Saml2\LogoutResponse - LogoutResponse.php

SAML 2 Logout Response class

• LogoutResponse - Constructs a Logout Response object (Initialize params from settings and if provided load the Logout Response)
• getIssuer - Gets the Issuer of the Logout Response.
• getStatus - Gets the Status of the Logout Response.
• isValid - Determines if the SAML LogoutResponse is valid
• build - Generates a Logout Response object.
• getResponse - Returns a Logout Response object.
• getErrorException - After executing a validation process, if it fails, this method returns the exception triggered.

Saml2\Settings - Settings.php

Configuration of the SAML PHP Toolkit

• Settings - Initializes the settings: Sets the paths of the different folders and Loads settings info from settings file or array/object provided
• checkSettings - Checks the settings info.
• getExtLibPath - Returns external lib path.
• checkSPCerts - Checks if the x509 certs of the SP exists and are valid.
• getSPkey - Returns the x509 private key of the SP.
• getSPcert - Returns the x509 public cert of the SP.
• getSPcertNew - Returns the future x509 public cert of the SP.
• getIdPData - Gets the IdP data.
• getSPDataGets the SP data.
• getSecurityData - Gets security data.
• getContacts - Gets contact data.
• getOrganization - Gets organization data.
• getSPMetadata - Gets the SP metadata. The XML representation.
• validateMetadata - Validates an XML SP Metadata.
• getErrors - Returns an array with the errors, the array is empty when the settings is ok.
• getLastErrorException - Returns the exception related to the last error
• getBaseURL - Returns the baseurl set on the settings if any.
• setStrict - Activates or deactivates the strict mode.
• isStrict - Returns if the 'strict' mode is active.

Saml2\Metadata - Metadata.php

A class that contains functionality related to the metadata of the SP

• builder - Generates the metadata of the SP based on the settings.
• signmetadata - Signs the metadata with the key/cert provided
• addX509KeyDescriptors - Adds the x509 descriptors (sign/encriptation) to the metadata

Saml2\Utils - Utils.php

Auxiliary class that contains several methods

• validateXML - This function attempts to validate an XML string against the specified schema.
• formatCert - Returns a x509 cert (adding header & footer if required).
• formatPrivateKey - returns a RSA private key (adding header & footer if required).
• redirect - Executes a redirection to the provided url (or return the target url).
• isHTTPS - Checks if https or http.
• getSelfHost - Returns the current host.
• getSelfURLhost - Returns the protocol + the current host + the port (if different than common ports).
• getSelfURLNoQuery - Returns the URL of the current host + current view.
• getSelfURL - Returns the URL of the current host + current view + query.
• generateUniqueID - Generates a unique string (used for example as ID for assertions).
• parseTime2SAML - Converts a UNIX timestamp to SAML2 timestamp on the form yyyy-mm-ddThh:mm:ss(\.s+)?Z.
• parseSAML2Time - Converts a SAML2 timestamp on the form yyyy-mm-ddThh:mm:ss(\.s+)?Z to a UNIX timestamp. The sub-second part is ignored.
• parseDuration - Interprets a ISO8601 duration value relative to a given timestamp.
• getExpireTime - Compares two dates and returns the earliest.
• query - Extracts nodes from the DOMDocument.
• isSessionStarted - Checks if the session is started or not.
• deleteLocalSession - Deletes the local session.
• calculateX509Fingerprint - Calculates the fingerprint of a x509cert.
• formatFingerPrint - Formats a fingerprint.
• generateNameId - Generates a nameID.
• getStatus - Gets Status from a Response.
• decryptElement - Decrypts an encrypted element.
• castKey - Converts a XMLSecurityKey to the correct algorithm.
• addSign - Adds signature key and senders certificate to an element (Message or Assertion).
• validateSign - Validates a signature (Message or Assertion).

Saml2\IdPMetadataParser - IdPMetadataParser.php

Auxiliary class that contains several methods to retrieve and process IdP metadata

• parseRemoteXML - Get IdP Metadata Info from URL.
• parseFileXML - Get IdP Metadata Info from File.
• parseXML - Get IdP Metadata Info from XML.
• injectIntoSettings - Inject metadata info into php-saml settings array.

For more info, look at the source code; each method is documented and details about what it does and how to use it are provided. Make sure to also check the doc folder where HTML documentation about the classes and methods is provided for SAML and SAML2.

Demos included in the toolkit

The toolkit includes three demo apps to teach how use the toolkit, take a look on it.

Demos require that SP and IdP are well configured before test it.

Demo1

SP setup

The SAML PHP Toolkit allows you to provide the settings info in two ways:

• Use a settings.php file that we should locate at the base folder of the toolkit.
• Use an array with the setting data.

In this demo we provide the data in the second way, using a setting array named $settingsInfo. This array users the settings_example.php included as a template to create the settings.php settings and store it in the demo1/ folder. Configure the SP part and later review the metadata of the IdP and complete the IdP info.

If you check the code of the index.php file you will see that the settings.php file is loaded in order to get the $settingsInfo var to be used in order to initialize the Setting class.

Notice that in this demo, the setting.php file that could be defined at the base folder of the toolkit is ignored.

IdP setup

Once the SP is configured, the metadata of the SP is published at the metadata.php file. Configure the IdP based on that information.

How it works

1. First time you access to index.php view, you can select to login and return to the same view or login and be redirected to the attrs.php view.

2. When you click:

   2.1 in the first link, we access to (index.php?sso) an AuthNRequest is sent to the IdP, we authenticate at the IdP and then a Response is sent through the user's client to the SP, specifically the Assertion Consumer Service view: index.php?acs. Notice that a RelayState parameter is set to the url that initiated the process, the index.php view.

   2.2 in the second link we access to (attrs.php) have the same process described at 2.1 with the diference that as RelayState is set the attrs.php.

3. The SAML Response is processed in the ACS (index.php?acs), if the Response is not valid, the process stops here and a message is shown. Otherwise we are redirected to the RelayState view. a) index.php or b) attrs.php.

4. We are logged in the app and the user attributes are showed. At this point, we can test the single log out functionality.

5. The single log out functionality could be tested by two ways.

   5.1 SLO Initiated by SP. Click on the "logout" link at the SP, after that a Logout Request is sent to the IdP, the session at the IdP is closed and replies through the client to the SP with a Logout Response (sent to the Single Logout Service endpoint). The SLS endpoint (index.php?sls) of the SP process the Logout Response and if is valid, close the user session of the local app. Notice that the SLO Workflow starts and ends at the SP.

   5.2 SLO Initiated by IdP. In this case, the action takes place on the IdP side, the logout process is initiated at the idP, sends a Logout Request to the SP (SLS endpoint, index.php?sls). The SLS endpoint of the SP process the Logout Request and if is valid, close the session of the user at the local app and send a Logout Response to the IdP (to the SLS endpoint of the IdP). The IdP receives the Logout Response, process it and close the session at of the IdP. Notice that the SLO Workflow starts and ends at the IdP.

Notice that all the SAML Requests and Responses are handled by a unique file, the index.php file and how GET paramters are used to know the action that must be done.

Demo2

SP setup

The SAML PHP Toolkit allows you to provide the settings info in two ways:

• Use a settings.php file that we should locate at the base folder of the toolkit.
• Use an array with the setting data.

The first is the case of the demo2 app. The setting.php file and the setting_extended.php file should be defined at the base folder of the toolkit. Review the setting_example.php and the advanced_settings_example.php to learn how to build them.

In this case as Attribute Consume Service and Single Logout Service we are going to use the files located in the endpoint folder (acs.php and sls.php).

IdP setup

Once the SP is configured, the metadata of the SP is published at the metadata.php file. Based on that info, configure the IdP.

How it works

At demo1, we saw how all the SAML Request and Responses were handler at an unique file, the index.php file. This demo1 uses high-level programming.

At demo2, we have several views: index.php, sso.php, slo.php, consume.php and metadata.php. As we said, we will use the endpoints that are defined in the toolkit (acs.php, sls.php of the endpoints folder). This demo2 uses low-level programming.

Notice that the SSO action can be initiated at index.php or sso.php.

The SAML workflow that take place is similar that the workflow defined in the demo1, only changes the targets.

1. When you access index.php or sso.php for the first time, an AuthNRequest is sent to the IdP automatically, (as RelayState is sent the origin url). We authenticate at the IdP and then a Response is sent to the SP, to the ACS endpoint, in this case acs.php of the endpoints folder.

2. The SAML Response is processed in the ACS, if the Response is not valid, the process stops here and a message is shown. Otherwise we are redirected to the RelayState view (sso.php or index.php). The sso.php detects if the user is logged and redirects to index.php, so we will be in the index.php at the end.

3. We are logged into the app and the user attributes (if any) are shown. At this point, we can test the single log out functionality.

4. The single log out functionality could be tested by two ways.

   4.1 SLO Initiated by SP. Click on the "logout" link at the SP, after that we are redirected to the slo.php view and there a Logout Request is sent to the IdP, the session at the IdP is closed and replies to the SP a Logout Response (sent to the Single Logout Service endpoint). In this case The SLS endpoint of the SP process the Logout Response and if is valid, close the user session of the local app. Notice that the SLO Workflow starts and ends at the SP.

   4.2 SLO Initiated by IdP. In this case, the action takes place on the IdP side, the logout process is initiated at the idP, sends a Logout Request to the SP (SLS endpoint sls.php of the endpoint folder). The SLS endpoint of the SP process the Logout Request and if is valid, close the session of the user at the local app and sends a Logout Response to the IdP (to the SLS endpoint of the IdP).The IdP receives the Logout Response, process it and close the session at of the IdP. Notice that the SLO Workflow starts and ends at the IdP.