API Management versions 7.5.X and 7.6.X have reached end of support in November 2020.
Check out the latest version of the documentation.

Configuration file elements

This section describes the elements in the service-provider-apiportal.xml configuration file.


This is the root element of the configuration descriptor. This section contains one <CertificateValidation> element (optional), one <ServiceProvider> element and one <IdentityProviders> element.


This element describes the certificate validation. You can configure certificate validation to validate the SP and IdP certificates at startup. The following attributes are supported:

Attribute Description

If set to true, the certification path for each certificate will be checked. If set to false, the agent verifies only the validity period of each certificate.

A trust store must be specified if this attribute is true.


If set to true, the agent also verifies if the certificates are not revoked.


The path to the trust store containing the trusted certificates.


The password to access the trust store.


The path to a store containing intermediate certificates that can appear in certificate chains.


The password to access the intermediate certificates store.


Defines at which interval certificate validation occurs, in hours.

To disable certificate validation, set pathValidation to false. For example:



This element describes the SP. The following attributes are supported:

Attribute Description

Sets the unique identifier of the SP. This identifier is sent to the IdP so it can know who is requesting an authentication or logging out. The default value is api-portal. The same value must also be set in the Joomla! Administrator Interface (JAI), see Enable SSO in API Portal.


An endpoint URI check examines the intended destination endpoint as determined by the IdP and the actual receiver endpoint for a message. In other words, where the message was intended and where it was actually delivered.

By default, the check mandates that these two values must match exactly. However, in the case of reverse proxying, the message destination endpoint server forwards the messages on for processing to another server, and the check must be relaxed slightly.

This setting specifies if that the host name in the message destination endpoint is not checked although the path is checked. Set this value to true.


This setting defines a CSV list of hosts that the host in the message destination endpoint is checked against.

This setting is optional. If you do not intend to use this, delete this attribute from the configuration file. This configuration is less secure but more flexible.

If you include the list of safe hosts, include the host details of your API Portal (https://<FQDN>:<port>) in the list. The endpoint URI check succeeds only if the host name in the message destination endpoint is on the list.


Delegates the session management to the application. The default value is true.


Specifies the URI of the SSO filter entry point for authentication. Set this value to /sso/externallogin.

The SSO filter only manages login URI, for other requests the application must redirect to SSO filter to manage authentication.

If the user is not authenticated, a SAML authentication request is built and sent to the IdP. Otherwise, the security token is forwarded to the application.


Specifies the URI of the SSO filter entry point for logout process. Set this value to /sso/externallogout.

The SSO filter generates a logout request and sends it to the IdP.


Specifies the URI where to redirect after the logout process. Set this value to /api/portal/v1.3/sso/proxylogout.


Specifies the name of a keystore where the private key of the SP is stored. The default value is conf/sso.jks.

The SP uses the private key to decrypt messages from the IdP that the IdP has encrypted with the SP's public key. If the IdP does not encrypt the messages, the keystore can be omitted.

When you set this attribute, the keystorePassphrase and keyAlias attributes must also be set.

The keystore must be in the classpath of the application or in its working directory. The keystore format must be .jks.

Specifies the password of the keystore, if a password is set.
Specifies the alias of the SP's private key in the keystore, if an alias is set.
Sets the name of the cookie where the SSO session identifier is stored if the SSO module is the session manager. The recommended value is spExternalSSOSessionId3.


This element specifies an entry point in API Portal for receiving SAML assertions from the IdP.


This element specifies the IdP URL where the logout responses are sent. Only HTTP-POST binding is managed.


This element describes the entity that exchanges SAML messages with the SSO filter. This section contains a section called <SamlIdentityProvider>, which supports the following attributes:




Sets the unique identifier of the IdP. These values must match the entityId and format values of the Issuer element in the SAML assertions.

If the SAML assertion does not have the format set, omit the format element.


Specifies the URL of the metadata file. The default value is ./idp.xml.


Specifies the name of the IdP attribute that provides the user name. The default value is urn:oid:

When a user is authenticated, the SSO filter sets a principal on the HttpServletRequest. By default, the name of this principal is extracted from the Subject element in the assertions of an authentication response. If userNameAttribute is set, the name of the principal is set to the value of the specified IdP attribute.

Verifies the validity period of a SAML assertion. The default value is true.


This element contains the mappings to be applied on the IdP attributes.


You can set extra features in the configuration file to fine-tune the SP and the IdPs.

Related Links