...
There are several extra properties that may need to be set to provide the additional bits of information to the runtime:. Note that you should check that a particular property is supported in the version of CXF you are using.
ws-security.username | The username used for UsernameToken policy assertions |
ws-security.password | The password used for UsernameToken policy assertions. If not specified, the callback handler will be called. |
ws-security.callback-handler | The WSS4J security CallbackHandler that will be used to retrieve passwords for keystores and UsernameTokens. |
ws-security.signature.properties | The properties file/object that contains the WSS4J properties for configuring the signature keystore and crypto objects |
ws-security.encryption.properties | The properties file/object that contains the WSS4J properties for configuring the encryption keystore and crypto objects |
ws-security.signature.username | The username or alias for the key in the signature keystore that will be used. If not specified, it uses the the default alias set in the properties file. If that's also not set, and the keystore only contains a single key, that key will be used. |
ws-security.encryption.username | The username or alias for the key in the encryption keystore that will be used. If not specified, it uses the the default alias set in the properties file. If that's also not set, and the keystore only contains a single key, that key will be used. For the web service provider, the useReqSigCert keyword can be used to accept (encrypt to) any client whose public key is in the service's truststore (defined in ws-security.encryption.properties.) |
ws-security.signature.crypto | Instead of specifying the signature properties, this can point to the full WSS4J Crypto object. This can allow easier "programmatic" configuration of the Crypto information." |
ws-security.encryption.crypto | Instead of specifying the encryption properties, this can point to the full WSS4J Crypto object. This can allow easier "programmatic" configuration of the Crypto information." |
ws-security.subject.cert.constraints | This configuration tag is a comma separated String of regular expressions which will be applied to the subject DN of the certificate used for signature validation, after trust verification of the certificate chain associated with the certificate. These constraints are not used when the certificate is contained in the keystore (direct trust). |
ws-security.is-bsp-compliant | Whether to ensure compliance with the Basic Security Profile (BSP) 1.1 or not. The default value is "true". |
ws-security.timestamp.futureTimeToLive | This configuration tag specifies the time in seconds in the future within which the Created time of an incoming Timestamp is valid. WSS4J rejects by default any timestamp which is "Created" in the future, and so there could potentially be |
Note: for Symmetric bindings that specify a protection token, the ws-security-encryption properties are used.
...