Configuring SAML

As noted in the previous tutorials, anything related to configuring SP connections must be done through the SAML Admin UI where configurations are saved to Liferay’s database. SP connections can no longer be made via properties files as they were in versions prior to 3.1.0.

This is an portal instance scoped configuration which can be managed via OSGi Configuration Admin. The affected properties are those in the SAMLProviderConfiguration metatype:

- `saml.keystore.credential.password`
- `saml.sp.assertion.signature.required`
- `saml.idp.authn.request.signature.required`
- `saml.sp.clock.skew`
- `saml.default.assertion.lifetime`
- ``
- `saml.enabled`
- ``
- `saml.sp.ldap.import.enabled`
- `saml.role`
- `saml.idp.session.maximum.age`
- `saml.idp.session.timeout`
- `saml.sp.sign.authn.request`
- `saml.sign.metadata`
- `saml.ssl.required`
- ``

The SAML Admin UI remains the place for creating the portal instance scoped configuration instances.

Note that there is also a system wide configuration, represented by the SamlConfiguration metatype.

If you used Liferay 6.2, please note that the following system wide properties were removed:

`saml.metadata.paths` (served no purpose after removal of SP connection defaults)

The latter two properties were replaced with the single property saml.runtime.metadata.refresh.interval.

Note also the introduction of the SAML KeyStoreManager Implementation Configuration in Control PanelSystem Settings. The options for this configuration are explained above in the Setting up Liferay DXP as a SAML Identity Provider section.

« Setting up Liferay DXP as a SAML Service ProviderLogging in to Liferay DXP »
Was this article helpful?
0 out of 0 found this helpful