Available in stable development 1.15 1.14 1.13 1.12 1.11 1.10 1.9 1.8 1.7 1.6

Metadata endpoints

This document gives a short introduction to the various methods forms metadata endpoints can take in SimpleSAMLphp.

The endpoints we have are:

Endpoint Indexed Default binding
ArtifactResolutionService Y SOAP
AssertionConsumerService Y HTTP-POST
SingleLogoutService N HTTP-Redirect
SingleSignOnService N HTTP-Redirect

The various endpoints can be specified in three different ways:

1 A single string

'AssertionConsumerService' => 'https://sp.example.org/ACS',

This is the simplest endpoint format. It can be used when there is only a single endpoint that uses the default binding.

2 Array of strings

'AssertionConsumerService' => array(
    'https://site1.example.org/ACS',
    'https://site2.example.org/ACS',
),

This endpoint format can be used to represent multiple endpoints, all of which use the default binding.

3 Array of arrays

'AssertionConsumerService' => array(
    array(
        'index' => 1,
        'isDefault' => TRUE,
        'Location' => 'https://sp.example.org/ACS',
        'Binding' => 'urn:oasis:names:tc:SAML:2.0:bindings:HTTP-POST',
    ),
    array(
        'index' => 2,
        'Location' => 'https://sp.example.org/ACS',
        'Binding' => 'urn:oasis:names:tc:SAML:2.0:bindings:HTTP-Artifact',
    ),
),

This endpoint format allows for specifying multiple endpoints with different bindings. It can also be used to specify the ResponseLocation attribute on endpoints, e.g. on SingleLogoutService:

'SingleLogoutService' => array(
    array(
        'Location' => 'https://sp.example.org/LogoutRequest',
        'ResponseLocation' => 'https://sp.example.org/LogoutResponse',
        'Binding' => 'urn:oasis:names:tc:SAML:2.0:bindings:HTTP-Redirect',
    ),
),