Re: [389-users] Existing certificate error

2011-08-09 Thread mallapadi niranjan
On Tue, Aug 9, 2011 at 2:46 PM, s.varadha rajan wrote: > Hi Niranjan, > > Thx for the reply and tried as per your steps.then i made changes in > dse.ldif as per wiki.After that, i restarted then i got the below error, > > * Starting 389 Directory Server instances : > [09/Aug/2011:14:41:18 +051800]

Re: [389-users] Existing certificate error

2011-08-09 Thread Carsten Grzemba
: Re: [389-users] Existing certificate error An: "General discussion list for the 389 Directory server project." <389-users@lists.fedoraproject.org> > Hi Niranjan, > > Thx for the reply and tried as per your steps.then i made changes in dse.ldif > as per wiki.After

Re: [389-users] Existing certificate error

2011-08-09 Thread s.varadha rajan
Hi Niranjan, Thx for the reply and tried as per your steps.then i made changes in dse.ldif as per wiki.After that, i restarted then i got the below error, * Starting 389 Directory Server instances : [09/Aug/2011:14:41:18 +051800] - SSL alert: Security Initialization: Unable to find slot Netscape

Re: [389-users] Existing certificate error

2011-08-08 Thread s.varadha rajan
Hi Niranjan, Password we have used while creating the certificate, that is not accepting. this is the problem. @Rob, We have the certificate in .p12 format and in that all are integrated. generally if you imported from .p12 everything should work. This is where i am struck and still facing the

Re: [389-users] Existing certificate error

2011-08-05 Thread mallapadi niranjan
Greetings, When clicking on "Manage certificates" From console for the first time, it would ask to set a password. after which you can create/request or import certificates. The certificates are stored in NSS database in /etc/dirsrv/slapd- So you need to know what was the original password tha

[389-users] Existing certificate error

2011-08-04 Thread s.varadha rajan
Hi, We are planning to configure ssl enabled Fedora directory server.we have a proper signed certificate.while importing, it is asking "Enter the password to access the Token" ? like that. even though we have given the exact password, while creating the certificate but it is not working. I referre