Skip to main content

Securing the Service Locator SOAP Service

The Service Locator SOAP Service provides additional security configuration.

Information noteWarning: The Service Locator REST service can not currently be secured.
Information noteNote: The configuration files described here are created in the container when you install the Service Locator SOAP Service component.

The predefined security configurations support two scenarios: using a UserName token or a SAML token. For switching between these scenarios and configuring additional security parameters use the etc/org.talend.esb.locator.service.cfg configuration file:

You can specify the following properties in that file:

Property name

Description

locator.authentication

NO (default) - No security scenario

SAML - SAML token scenario

TOKEN - UserName token scenario

policy.token

Location of the UserName token scenario policy file.

policy.saml

Location of the SAML token scenario policy file.

security.signature.properties

Link to the properties file which contains signature parameters. Used for SAML token verification. Default value is file:${tesb.home}/etc/keystores/serviceKeystore.properties.

security.signature.username

SAML token signature username. Used for SAML token verification.

security.signature.password

SAML token signature password. Used for SAML token verification.

The UserName token policy is located and can be configured here: etc/org.talend.esb.locator.token.policy.

The SAML token policy is located and can be configured here: etc/org.talend.esb.locator.saml.policy.

Did this page help you?

If you find any issues with this page or its content – a typo, a missing step, or a technical error – please let us know!