Ellisith
6 years agoOccasional Visitor
Message Layer Encryption
I've been working with Message Layer Encryption with SOAPui.
I think I have everything configured properly on the server side, but when I try to connect to it, I get different errors if I use IIB or SoapUI's client to connect. Honestly, I'm not sure what these errors mean, particularly the first one.
If anyone has any ideas, I'd love to hear them!
With SoapUI, I get:
- Mon Jul 08 15:31:39 EDT 2019:ERROR:org.apache.ws.security.WSSecurityException: An invalid security token was provided (Bad ValueType "http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-x509-token-profile-1.0#X509v3")
- org.apache.ws.security.WSSecurityException: An invalid security token was provided (Bad ValueType "http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-x509-token-profile-1.0#X509v3")
- at org.apache.ws.security.str.BSPEnforcer.checkBinarySecurityBSPCompliance(BSPEnforcer.java:70)
- at org.apache.ws.security.str.SignatureSTRParser.parseBSTKeyIdentifier(SignatureSTRParser.java:383)
- at org.apache.ws.security.str.SignatureSTRParser.parseSecurityTokenReference(SignatureSTRParser.java:219)
- at org.apache.ws.security.processor.SignatureProcessor.handleToken(SignatureProcessor.java:169)
With IIB, I get:
- Mon Jul 08 15:29:10 EDT 2019:ERROR:org.apache.ws.security.WSSecurityException: The signature or decryption was invalid
- org.apache.ws.security.WSSecurityException: The signature or decryption was invalid
- at org.apache.ws.security.processor.SignatureProcessor.verifyXMLSignature(SignatureProcessor.java:447)
- at org.apache.ws.security.processor.SignatureProcessor.handleToken(SignatureProcessor.java:230)