** Anthony,
we had the same issue. Spent quite a bit of time on it and only way to make this working was to actually run Netscape on the Remedy server and connecting to the LDAP server from there, i.e. typing https://ldapservername:port <https://ldapservername:port/> to the address (port number I think should be 636). Netscape then asked if the site is trusted and we wanted to update the certificate. After this, the certificate database file got updated and Remedy then could login to the LDAP server through SSH. Hope this helps. Regards Jiri Pospisil Technology Support Systems ▪T▪ ▪ ▪Mobile UK▪ -----Original Message----- From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Anthony K R Sent: 01 February 2007 16:19 To: [email protected] Subject: AREA LDAP with SSL Hi, OS: Redhat Linux ARS: 5.01.02 with Patch 1389 We have configured AREA LDAP without SSL and it works fine. To enable SSL, we have to use our certificates. The Security team is unable to import these certificates into to Netscape's( v 4.79 )cert7.db and key3.db files. When they use CertUtil to view cert7.db, they see all the information but when our certificates are added, the tool always gives cert8.db but not cert7.db. I have explored the previous posts available in ARSList/RemedySupport about SSL, but don't know how to update certificate database. When I try to import certificates through Netscape Communicator, it does not work. If you know how to import certificates to cert7.db, please let me know. Regards, Anthony __20060125_______________________This posting was submitted with HTML in it___ NOTICE AND DISCLAIMER: This email (including attachments) is confidential. If you have received this email in error please notify the sender immediately and delete this email from your system without copying or disseminating it or placing any reliance upon its contents. We cannot accept liability for any breaches of confidence arising through use of email. Any opinions expressed in this email (including attachments) are those of the author and do not necessarily reflect our opinions. We will not accept responsibility for any commitments made by our employees outside the scope of our business. We do not warrant the accuracy or completeness of such information.
