Contributions
WS 1.1 Security
SOAPUI does not seem to support WS 1.1 security completely. In WS 1.1 security the initiator (client) generates a symmetric key and encrypts it with the server public key. The symmetric key is then used for both Encrypting and Signing the message. SOAPUI does not seem to support the Signing using the generated symmetric key. However the encryption support is available via the Symmetric Encoding Algorithm. A new option should be added which allows the Symmetric / SecretKey to be referenced from the generated symmetric key instead of a hardcoded value from a keystore. The Encryption options support some kind of Embedded KeyInfo but I can't see any documentation that explains what this does.10 years agoPlace ReadyAPI QuestionsReadyAPI Questions1.4KViews0likes1CommentSecretKey not supported due to JCEKS keystores not supported
Hello, I am trying to implement Outoing WS-Security to comply with the OWSM "oracle/wss11_username_token_with_message_protection_service_policy" which requires the Signature algorithm of "http://www.w3.org/2000/09/xmldsig#hmac-sha1" The algorithm requires a SecretKey. However it appears that the free version does not support a JCEKS keystore type and only supports a JKS keystore. A JKS keystore doesn't support SecretKeys. SOAPUI does however offer the option to use the signature algorithm. To summarise: JKS does not support SecretKeys HMAC-SHA1 needs a SecretKey SOAPUI supports HMAC-SHA1 but does not support a JCEKS keystore, so there is no way to get a secret key, hence will fail. If you try and import a JCEKS keystore you will not be able to access the store due to SOAPUI thinking its a JKS keystore not a JCEKS.11 years agoPlace ReadyAPI QuestionsReadyAPI Questions5.2KViews1like7Comments