Hi,
If this is not the right mailing list I apologize.
I have a problem with signed SOAP response from JBoss native stack
(JBoss WS implementation).
The X509 signed SOAP client call (Axis2 1.4 and Rampart 1.4) is
correctly sent and understood by the server.
The response contains X509 base 64 encoded certificate that WSS4j
fails to parse.
If I bypass invocation of
public X509Certificate getX509Certificate(Crypto crypto) throws
WSSecurityException
in
org.apache.ws.security.message.token.X509Security
which gets invoked by
org.apache.ws.security.processor .SignatureProcessor
in
public X509Certificate[] getCertificatesTokenReference(Element elem,
Crypto crypto)
and
org.apache.ws.security.processor.BinarySecurityTokenProcessor
in
public X509Certificate[] getCertificatesTokenReference(Element elem,
Crypto crypto)
with my own (quick, naive and dirty) X509 parsing implementation, then
SOAP response
passes the Apache Rampart processing.
I'm using WSS4j 1.5.7 and JBossWS 3.1.2 GA
Where can I post this potential bug?
What is the correct/standard binary format of the X509 certificate
that gets
base64 encoded in SOAP WS-Securtity header when using signing?
Thanks for reply,
Nikola Ivačič
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
