Thanks for the quick reply Werner. My point of reference was the x509 token profile 1.0 section 3.2.3, which prefers the x509 issuer/serial reference be wrapped in an <X509Data> element. I do see, however, that they disregard this guidance in 3.4 Encryption, and wss4j is consistent with this example. I do see that in the 1.1 spec http://www.oasis-open.org/committees/download.php/15253/oasis-wss-x509-token-profile-1.1.pdf it appears they've cleaned this up.
Unfortunately, WebLogic 9.0 does generate and expect the <X509Data> element, and because of the ambiguity in the spec, I can't exactly open an SR against them for this. Ah well. -Alex -----Original Message----- From: Dittmann, Werner [mailto:[EMAIL PROTECTED] Sent: Monday, January 23, 2006 8:55 AM To: Alex Horwitz; [email protected] Subject: AW: X509Data in Encryption KeyInfo Alex, the X509Data element is a contaier that can hold several data types. Currently WSS4J support the IssuerSerial data inside a X509Data - other data elements / types are not defined by the WS Security specifications (V1.0 specs). Regards, Werner > -----Ursprüngliche Nachricht----- > Von: Alex Horwitz [mailto:[EMAIL PROTECTED] > Gesendet: Montag, 23. Januar 2006 14:44 > An: [email protected] > Betreff: X509Data in Encryption KeyInfo > > Hello All! > > This issue has come up before: > > http://mail-archives.apache.org/mod_mbox/ws-fx-dev/200409.mbox /%3c79D5F4B2D775204D9C7852EE41C5477303E9D459> @mchh2a1e.mchh.siemens.de%3e > > but, essentially, I'm testing interoperability between > WebLogic 9.0 and Axis1.2.1/WSS4J1.1, and my only roadblock is > the inability of WSS4J to consume/generate the X509Data > element in the EncryptedKey/KeyInfo/SecurityTokenReference/ . > Has anyone else encountered this problem? Or, more > modestly, is this a problem in my interpretation or did I > ignorantly miss a more recent follow-up that clarifies this issue. > > Thanks very much for you help. > > -Alex > > --------------------------------------------------------------------- > 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] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
