Re: [ebxmlms-develop] Client certificate authentication

[Patrick Y. <kc...@ce...>]

Client certificate authenticationNot here. So, it will be great if you =
can help to look into this. Of course, we are more than happy to discuss =
with you on how to do it. Many thanks.
Regards, -Patrick
  ----- Original Message -----=20
  From: Ronald van Kuijk=20
  To: 'ebx...@li...'=20
  Sent: Monday, March 17, 2003 09:36 PM
  Subject: RE: [ebxmlms-develop] Client certificate authentication


  Anyone already started working on this... Otherwise I'll be glad to =
look a little into this since we need it as well?
    -----Oorspronkelijk bericht-----
    Van: Patrick Yee [mailto:kc...@ce...]
    Verzonden: woensdag 12 maart 2003 6:02
    Aan: ebx...@li...
    Onderwerp: Re: [ebxmlms-develop] Client certificate authentication


    Unfortunately, Hermes is not supporting the use of client =
certificate authentication right now. -Patrick
      ----- Original Message -----=20
      From: Mayne, Peter=20
      To: 'ebx...@li...'=20
      Sent: Wednesday, March 12, 2003 12:55 PM
      Subject: [ebxmlms-develop] Client certificate authentication


      I'm trying to send ebXML messages to an HTTPS site that requires =
client certificate authentication.=20

      I have the HTTPS part working, but only by putting the web site's =
certificate's CA certificate in the JAVA_HOME\jre\lib\security\cacerts =
file. Hermes doesn't seem to be seeing my definitions of =
javax.net.ssl.trustStore and javax.net.ssl.trustStorePassword.

      Since it doesn't see those definitions, it probably won't see my =
definition of javax.net.ssl.keyStore et al either.=20

      What is the recommended way of telling Hermes where a trustStore =
is, and what client certificate to use when authenticating to an HTTPS =
site?

      Thanks.=20

      PJDM=20
      --=20
      Peter Mayne=20
      Technology Consultant=20
      Spherion Technology Solutions=20
      Level 1, 243 Northbourne Avenue, Lyneham, ACT, 2602=20
      T: 61 2 62689727  F: 61 2 62689777=20

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,=20
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=20
under the Privacy Act 1988 (Cth). Consent is hereby given by the =
recipient(s) to=20
collect, hold and use such information and any personal information =
contained in a=20
response to this email, for any reasonable purpose in the ordinary =
course of=20
Spherion's=20
business, including forwarding this email internally or disclosing it to =
a third party. All=20
personal information collected by Spherion will be handled in accordance =
with=20
Spherion's Privacy Policy. If you have received this email in error, =
please notify the=20
sender and delete it.

(c) you agree not to employ or arrange employment for any candidate(s) =
supplied in=20
this email and any attachments without first entering into a contractual =
agreement with=20
Spherion. You further agree not to divulge any information contained in =
this document=20
to any person(s) or entities without the express permission of Spherion.