<application-policy name="saml-validate-token">
<authentication>
<login-module code="org.picketlink.identity.federation.core.wstrust.auth.STSValidatingLoginModule" flag="required">
<module-option name="configFile">picketlink-sts-client.properties</module-option>
</login-module>
</authentication>
</application-policy>
And in jboss-esb.xml:
<service category="SamlSecurityQuickstart" name="securedSamlService" invmScope="GLOBAL"
description="This service demonstrates that an ESB service can be configured to only validate a security token.">
<security moduleName="saml-validate-token" callbackHandler="org.jboss.soa.esb.services.security.auth.login.JBossSTSTokenCallbackHandler">
<!-- disable the security context timeout so that our security context is re-evaluated -->
<property name="org.jboss.soa.esb.services.security.contextTimeout" value="0"/>
</security>
...
</service>
<application-policy name="saml-validate-token">
<authentication>
<login-module code="org.picketlink.identity.federation.core.wstrust.auth.STSValidatingLoginModule" flag="required">
<module-option name="configFile">picketlink-sts-client.properties</module-option>
</login-module>
</authentication>
</application-policy>
And in jboss-esb.xml:
<service category="SamlSecurityQuickstart" name="securedSamlService" invmScope="GLOBAL"
description="This service demonstrates that an ESB service can be configured to only validate a security token.">
<security moduleName="saml-validate-token" callbackHandler="org.jboss.soa.esb.services.security.auth.login.JBossSTSTokenCallbackHandler">
<!-- disable the security context timeout so that our security context is re-evaluated -->
<property name="org.jboss.soa.esb.services.security.contextTimeout" value="0"/>
</security>
...
</service>
Copy to ClipboardCopied!Toggle word wrapToggle overflow