[
https://issues.apache.org/jira/browse/WSS-81?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12506489
]
angélique commented on WSS-81:
------------------------------
Ok, thanks, I am going to try it with the last version of wss4j.
-----Message d'origine-----
De : Dittmann, Werner (JIRA) [mailto:[EMAIL PROTECTED]
Envoyé : mercredi 20 juin 2007 12:47
À : Jard Angélique
Objet : [jira] Commented: (WSS-81) Compatibility between WSS4J and WebLogic 9
for Encryption
[
https://issues.apache.org/jira/browse/WSS-81?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12506479
]
Dittmann, Werner commented on WSS-81:
-------------------------------------
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
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
> 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-200401-wss-soap-message-security-1.0#Base64Binary";>
> XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
> </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]
