|
From: Patrick Y. <kc...@ce...> - 2003-05-13 01:42:59
|
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> <html> <head> <meta http-equiv="Content-Type" content="text/html;charset=ISO-8859-1"> <title></title> </head> <body> Hmm.. the specification permits us to do what we are doing now, right? If this is true, how come the TIBCO one rejects a legal message? :-) OK, let's accept it as is, and the only thing we can change now is Hermes.<br> <br> It seems that it is no easy way. It is not related to PublicKeyFinder. Let's call it "key info formatter". So, does it make sense to add another hook (!!) to customize this part?<br> <br> What do you think about the "external hook" approach? Are there too many?<br> <br> Regards, -Patrick<br> <br> <br> Mayne, Peter wrote:<br> <blockquote type="cite" cite="mid...@s-..."> <meta http-equiv="Content-Type" content="text/html; "> <meta name="Generator" content="MS Exchange Server version 5.5.2654.45"> <title>RE: [ebxmlms-develop] Initialisation + customisation</title> <p><font size="2">No. When I'm sending a signed message, I want to determine whether the <a class="moz-txt-link-rfc2396E" href="ds:KeyInfo"><ds:KeyInfo></a> section is included in the message or not.</font></p> <p><font size="2">Given that Hermes currently has no database of CPA parameters (which is a discussion for another day), it might make sense to provide a parameter to Request.setSign() (and therefore to EbXmlMessage.sign(), and therefore to Signature.sign(), and therefore to PKISignatureImpl.sign(), and therefore (finally) to ApacheXMLDSigner.sign()) to specify whether the <a class="moz-txt-link-rfc2396E" href="ds:KeyInfo"><ds:KeyInfo></a> section is added or not. Hmm, that's a long chain of changes...</font></p> <p><font size="2">For now, I've just commented out the section of code in ApacheXMLDSigner that does the "signature.addKeyInfo((X509Certificate) certificates[i]);", but that only works while we have a single trading partner.</font></p> <p><font size="2">Incidentally, the trading partner's MSH is TIBCO BusinessConnect, which seems to have some interesting assumptions of it's own. For instance, where Hermes (pre-PublicKeyFinder) requires that the <a class="moz-txt-link-rfc2396E" href="ds:KeyInfo"><ds:KeyInfo></a> section is present, BusinessConnect requires that it *isn't* present. Hence, this new requirement for Hermes.</font></p> <p><font size="2">PJDM</font> <br> <font size="2">--</font> <br> <font size="2">Peter Mayne</font> <br> <font size="2">Technology Consultant</font> <br> <font size="2">Spherion Technology Solutions</font> <br> <font size="2">Level 1, 243 Northbourne Avenue, Lyneham, ACT, 2602</font> <br> <font size="2">T: 61 2 62689727 F: 61 2 62689777 </font> <br> <font size="2">-----Original Message-----</font> <br> <font size="2">From: Patrick Yee [<a href="mailto:kc...@ce...">mailto:kc...@ce...</a>]</font> <br> <font size="2">Sent: Tuesday, 13 May 2003 1:34 AM</font> <br> <font size="2">To: <a class="moz-txt-link-abbreviated" href="mailto:ebx...@li...">ebx...@li...</a></font> <br> <font size="2">Subject: Re: [ebxmlms-develop] Initialisation + customisation</font> </p> <br> <p><font size="2">Sorry, I am not sure about what you want it to be. Do you mean you want to make the verification of digital signature optional, on a per-CPA basis?</font></p> <p><font size="2">Regards, -Patrick</font> <br> <font size="2">Our trading partner can't accept messages with <a class="moz-txt-link-rfc2396E" href="ds:KeyInfo"><ds:KeyInfo></a> in them. It's easy enough to comment out this bit of code, but it would be nice to do it on a per-CPA basis. However, I'm not sure what the best way of specifying this would be. Any suggestions?</font></p> <font size="3" color="BLUE"> <pre>The information contained in this email and any attachments to it: (a) may be confidential and if you are not the intended recipient, any interference with, use, disclosure or copying of this material is unauthorised and prohibited; and (b) may contain personal information of the recipient and/or the sender as defined under the Privacy Act 1988 (Cth). Consent is hereby given by the recipient(s) to collect, hold and use such information and any personal information contained in a response to this email, for any reasonable purpose in the ordinary course of Spherion's business, including forwarding this email internally or disclosing it to a third party. All personal information collected by Spherion will be handled in accordance with Spherion's Privacy Policy. If you have received this email in error, please notify the sender and delete it. (c) you agree not to employ or arrange employment for any candidate(s) supplied in this email and any attachments without first entering into a contractual agreement with Spherion. You further agree not to divulge any information contained in this document to any person(s) or entities without the express permission of Spherion. </pre> </font> </blockquote> </body> </html> |