Re: [ebxmlms-develop] Initialisation + customisation

SourceForge Headquarters 1320 Columbia Street Suite 310 San Diego, CA 92101 +1 (858) 422-6466

<!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. 
 
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? 
 
What do you think about the "external hook" approach? Are there too
many? 
 
Regards, -Patrick 
 
 
Mayne, Peter wrote: 
<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>
 No. When I'm sending a signed message, I want to
determine whether the <a class="moz-txt-link-rfc2396E" href="ds:KeyInfo">&lt;ds:KeyInfo&gt;</a> section is included in the
message or not.
 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(),&nbsp; and therefore
to PKISignatureImpl.sign(), and therefore (finally) to
ApacheXMLDSigner.sign()) to specify whether the <a class="moz-txt-link-rfc2396E" href="ds:KeyInfo">&lt;ds:KeyInfo&gt;</a>
section is added or not. Hmm, that's a long chain of changes...
 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.
 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">&lt;ds:KeyInfo&gt;</a> section is present, BusinessConnect
requires that it *isn't* present. Hence, this new requirement for
Hermes.
 PJDM 
 -- 
 Peter Mayne 
 Technology Consultant 
 Spherion Technology Solutions 
 Level 1, 243 Northbourne Avenue, Lyneham, ACT, 2602 
 T: 61 2 62689727&nbsp; F: 61 2 62689777 
 -----Original Message----- 
 From: Patrick Yee [<a href="mailto:kc...@ce...">mailto:kc...@ce...</a>] 
 Sent: Tuesday, 13 May 2003 1:34 AM 
 To: <a class="moz-txt-link-abbreviated" href="mailto:ebx...@li...">ebx...@li...</a> 
 Subject: Re: [ebxmlms-develop] Initialisation +
customisation 
 
 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?
 Regards, -Patrick 
 Our trading partner can't accept messages with
<a class="moz-txt-link-rfc2396E" href="ds:KeyInfo">&lt;ds:KeyInfo&gt;</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?
 
 <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>