I've added some more information to the Java file. In fact you case use "DirectReference" for the encryption key id as well. The documentation was outdated, that's why I updated it int SVN (this is the source code repository).
Regards, Werner > -----Ursprüngliche Nachricht----- > Von: ext angélique (JIRA) [mailto:[EMAIL PROTECTED] > Gesendet: Mittwoch, 20. Juni 2007 11:50 > An: [email protected] > Betreff: [jira] Reopened: (WSS-81) Compatibility between > WSS4J and WebLogic 9 for Encryption > > > [ > https://issues.apache.org/jira/browse/WSS-81?page=com.atlassia > n.jira.plugin.system.issuetabpanels:all-tabpanel ] > > angélique reopened WSS-81: > -------------------------- > > > In the javadoc, I read ( WSHandlerConstants =>ENC_KEY_ID): > "For encryption IssuerSerial and X509KeyIdentifier are valid only." > > I tried both of them, and the BinarySecurityToken never appears..... > > The only propertie that create the BinarySecurityToken > element is encryptionKeyIdentifier=DirectReference, but it's > for Signing and I don't want to sign, I just want to encrypt. > > How can I encrypt a SOAP message with WSS4J to match the > request expected by the Web logic server ? > > > Compatibility between WSS4J and WebLogic 9 for Encryption > > --------------------------------------------------------- > > > > Key: WSS-81 > > URL: https://issues.apache.org/jira/browse/WSS-81 > > Project: WSS4J > > Issue Type: Bug > > Environment: Web service serveur: Web Logic 9 > > Web service client : axis+wss4j+bouncy castle on linux > > Reporter: angélique > > Assignee: Werner Dittmann > > Priority: Blocker > > > > Hello, > > There is a problem of compatibility between Web Logic 9 and WSS4J. > > One one hand, when a weblogic server is configured to do > encryption only, the SOAP message generated contain a xml > node like this: > > <wsse:BinarySecurityToken wsu:Id="bst_JFDmu9E2O5K4Opex" > xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401 > -wss-wssecurity-utility-1.0.xsd" > ValueType="http://docs.oasis-open.org/wss/2004/01/oasis-200401 > -wss-x509-token-profile-1.0#X509v3" > EncodingType="http://docs.oasis-open.org/wss/2004/01/oasis-200 > 401-wss-soap-message-security-1.0#Base64Binary"> > > > XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX > XXXXXXXXXXX > > </wsse:BinarySecurityToken> > > On the other hand, it's only possible with WSS4J to add the > token for signature. When using encryption alone, configuring > the client to send a SOAP message with this > BinarySecurityToken is not possible. > > Wath can I do to make a SOAP request whith an Encrypted > body AND a BinarySecurityToken in the <head> part ? > > Regards, > > Angélique > > -- > This message is automatically generated by JIRA. > - > You can reply to this email to add a comment to the issue online. > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
