OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

wss message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: FW: BinarySecurityToken attributes


Title: FW: BinarySecurityToken attributes

Typo in "OASIS X509 Token Profile v1.0" lines 308, 309. The sample still uses QName's

-- dims

---------- Forwarded message ----------
From: Rami Jaamour <rjaamour@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







[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]