You are viewing a plain text version of this content. The canonical link for it is here.
Posted to fx-dev@ws.apache.org by Rami Jaamour <rj...@parasoft.com> on 2004/05/03 22:03:05 UTC
BinarySecurityToken attributes
Hello,
There is an interoperability issue with WSS4J with regards to the
EncodingType and Value type attributes in the BinarySecurityToken
element in encryption and signature headers.
Currently WSS4J uses the values:
EncodingType="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-soap-message-security-1.0#Base64Binary"
ValueType="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-x509-token-profile-1.0#X509v3"
but the example in OASIS X509 Token Profile v1.0, lines 308, 309 uses
the values:
ValueType="wsse:X509v3"
EncodingType="wsse:Base64Binary"
Are these expected to be equivalent or is WSS4J incorrect in this matter?
Best Regards,
--
Rami Jaamour
Software Engineer
SOAPtest <http://www.parasoft.com/jsp/products/home.jsp?product=SOAP>
Development
Parasoft Corporation <http://www.parasoft.com>
/
We Make Software Work/
Re: BinarySecurityToken attributes
Posted by Davanum Srinivas <da...@gmail.com>.
yep
----- Original Message -----
From: Rami Jaamour <rj...@parasoft.com>
Date: Mon, 03 May 2004 13:36:13 -0700
Subject: Re: BinarySecurityToken attributes
To: dims@apache.org
Cc: fx-dev@ws.apache.org
So using
ValueType="wsse:X509v3"
EncodingType="wsse:Base64Binary"
Is wrong?
Rami Jaamour
Software Engineer
SOAPtest
Development
Parasoft Corporation
We Make Software Work
Davanum Srinivas wrote:
yep. it's a typo in the sample.
-- dims
----- Original Message -----
From: Rami Jaamour <rj...@parasoft.com>
Date: Mon, 03 May 2004 13:03:05 -0700
Subject: BinarySecurityToken attributes
To: fx-dev@ws.apache.org
Hello,
There is an interoperability issue with WSS4J with regards to the
EncodingType and Value type attributes in the BinarySecurityToken
element in encryption and signature headers.
Currently WSS4J uses the values:
EncodingType="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-soap-message-security-1.0#Base64Binary"
ValueType="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-x509-token-profile-1.0#X509v3"
but the example in OASIS X509 Token Profile v1.0, lines 308, 309 uses
the values:
ValueType="wsse:X509v3"
EncodingType="wsse:Base64Binary"
Are these expected to be equivalent or is WSS4J incorrect in this
matter?
Best Regards,
Re: BinarySecurityToken attributes
Posted by Rami Jaamour <rj...@parasoft.com>.
So using
ValueType="wsse:X509v3"
EncodingType="wsse:Base64Binary"
Is wrong?
Rami Jaamour
Software Engineer
SOAPtest <http://www.parasoft.com/jsp/products/home.jsp?product=SOAP>
Development
Parasoft Corporation <http://www.parasoft.com>
/
We Make Software Work/
Davanum Srinivas wrote:
>yep. it's a typo in the sample.
>
>-- dims
>
>
>----- Original Message -----
>From: Rami Jaamour <rj...@parasoft.com>
>Date: Mon, 03 May 2004 13:03:05 -0700
>Subject: BinarySecurityToken attributes
>To: fx-dev@ws.apache.org
>
>
>
>
>
>
>
>
>
>Hello,
>
>
>
>There is an interoperability issue with WSS4J with regards to the
>EncodingType and Value type attributes in the BinarySecurityToken
>element in encryption and signature headers.
>
>
>
>Currently WSS4J uses the values:
>
>
>
>EncodingType="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-soap-message-security-1.0#Base64Binary"
>
>ValueType="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-x509-token-profile-1.0#X509v3"
>
>
>
>but the example in OASIS X509 Token Profile v1.0, lines 308, 309 uses
>the values:
>
>
>
>ValueType="wsse:X509v3"
>
>EncodingType="wsse:Base64Binary"
>
>
>
>Are these expected to be equivalent or is WSS4J incorrect in this
>matter?
>
>
>
>
>
>Best Regards,
>
>
>
>
Re: BinarySecurityToken attributes
Posted by Davanum Srinivas <da...@gmail.com>.
yep. it's a typo in the sample.
-- dims
----- Original Message -----
From: Rami Jaamour <rj...@parasoft.com>
Date: Mon, 03 May 2004 13:03:05 -0700
Subject: BinarySecurityToken attributes
To: fx-dev@ws.apache.org
Hello,
There is an interoperability issue with WSS4J with regards to the
EncodingType and Value type attributes in the BinarySecurityToken
element in encryption and signature headers.
Currently WSS4J uses the values:
EncodingType="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-soap-message-security-1.0#Base64Binary"
ValueType="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-x509-token-profile-1.0#X509v3"
but the example in OASIS X509 Token Profile v1.0, lines 308, 309 uses
the values:
ValueType="wsse:X509v3"
EncodingType="wsse:Base64Binary"
Are these expected to be equivalent or is WSS4J incorrect in this
matter?
Best Regards,
--
Rami Jaamour
Software Engineer
SOAPtest
Development
Parasoft Corporation
We Make Software Work