For production use, the sample keys used here will need to be replaced with your project's own keys, usually signed by a third-party CA.
To enable Security Token Service in the Talend Runtime, you need to deploy it into a Talend Runtime container:
Replace the STS' sample keystore/truststore called
stsstore.jkslocated in the
<TalendRuntimePath>/container/etc/keystoresfolder with your own keystore. See Security Token Service Configuration for more information.
<TalendRuntimePath>/container/bindirectory, enter trun to start Talend Runtime, a Talend Runtime container (Karaf) console window will open.
In the console, type tesb:start-sts to install the Security Token Service feature. Or type feature:install tesb-sts if you are using a generic Karaf container instead of Talend Runtime
Type list | grep STS in the console. You should see the following output:
ID State Blueprint Spring Level Name [ 203] [Active ] [ ] [started ] [ 60] Apache CXF STS Core (2.5.0) Fragments: 204 [ 204] [Resolved ] [ ] [ ] [ 60] Talend :: ESB :: STS :: CONFIG (6.3.2)
The above shows that the Security Token Service feature is enabled in the Talend Runtime container. The Fragment Bundle
204: Talend :: ESB :: STS :: CONFIG (6.3.2)provides the custom configuration about the Security Token Service, which will be described in Security Token Service Configuration.