We are running Remedy 7.6.04 on a Red Hat Linux platform with the latest java and have need to consume an external web service that is written in .net. The external server needs a server certificate to allow our machines to talk, this is working. The .net application then wants a client certificate to come over to allow access to the application. From what we can tell, both certificates are cleared via the certificate authority, but the client certificate does not appear to be passed or something. Unfortunately once the server certificate goes, the connection is buried in ssl and we cannot get a clean trace to see if there is an error with the client certificate. The Remedy error message we get back is 403 Forbidden. We have written some code in .net on our side to prove that a connection with this client certificate is possible, but to get that to work we had to define the certificate as X509_Certificate2. Has anyone had any luck getting remedy on linux to talk to an external web service using this type of client certificate and a server certificate? This is becoming urgent.
Thanks Bob Ellington (RSP) bob.elling...@gmail.com _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug11 www.wwrug.com ARSList: "Where the Answers Are"
