Yay! I'm glad this got you moving, and you are back in business! Hope I helped!
> On 23 Aug 2019, at 14:37, Fernando Fuentes wrote:
>
> William,
>
> Delete the CA and re-added it and worked. We are back in business.
>
> Thanks for all your help!
>
> On 8/22/19 11:27 PM, Fernando Fuentes wrot
William,
Delete the CA and re-added it and worked. We are back in business.
Thanks for all your help!
On 8/22/19 11:27 PM, Fernando Fuentes wrote:
William,
I got a bit further!
I follow this:
https://access.redhat.com/documentation/en-us/red_hat_directory_server/10/html/administration_guide
William,
I got a bit further!
I follow this:
https://access.redhat.com/documentation/en-us/red_hat_directory_server/10/html/administration_guide/AdminServerConfig#Using-the-DS-Key-Cert-for-Admin-Server
And I added the password.conf part and it seem to have work. BUT I got:
[Thu Aug 22 18:23:
Thanks William!
I shall await for his glorious entrance :D
Thanks again!
Regards,
-
On 8/22/19 11:18 PM, William Brown wrote:
It might be best to wait for Mark Reynolds to have a look, he's the admin
server expert :)
On 23 Aug 2019, at 14:13, Fernando Fuentes wrote:
William,
Understood,
It might be best to wait for Mark Reynolds to have a look, he's the admin
server expert :)
> On 23 Aug 2019, at 14:13, Fernando Fuentes wrote:
>
> William,
>
> Understood, But it still does not do anything for me. I keep getting the same
> error.
> I am not sure is even been loaded.
>
> Is
William,
Understood, But it still does not do anything for me. I keep getting the
same error.
I am not sure is even been loaded.
Is there a way i can find that is looking for this pin file?
Thanks!
On 8/22/19 11:10 PM, William Brown wrote:
Yes, but that format of the pin.txt is what svrcore
Yes, but that format of the pin.txt is what svrcore experts when you start the
admin server.
pin.txt -> svrcore -> admin server
pwdfile.txt -> certutil
They do seperate things :)
It's lovely and confusing :)
> On 23 Aug 2019, at 13:17, Fernando Fuentes wrote:
>
> William,
>
> Thanks for y
William,
Thanks for your reply.
If I use the pin file with that format I get:
[root@hypersouth admin-serv]# certutil -K -d . -f pin.txt
certutil: Checking token "NSS Certificate DB" in slot "NSS User Private
Key and Certificate Services"
Incorrect password/PIN entered.
certutil: could not auth
Try /etc/dirsrv/admin-serv/pin.txt with the format:
Internal (Software) Token:PASSWORD
> On 23 Aug 2019, at 13:12, Fernando Fuentes wrote:
>
> Just to show that I got the password right :)
>
> [root@hypersouth admin-serv]# certutil -K -d . -f pwdfile.txt
> certutil: Checking token "NSS Certifi
Just to show that I got the password right :)
[root@hypersouth admin-serv]# certutil -K -d . -f pwdfile.txt
certutil: Checking token "NSS Certificate DB" in slot "NSS User Private
Key and Certificate Services"
< 0> rsa ec05a16fff5a6756702d91a127e4a5dbf8e93380 hypersouthCert
[root@hypersout
Even after I reset the databse and set new password:
[Thu Aug 22 22:08:45.149745 2019] [:error] [pid 13011:tid
140251715872896] Password for slot internal is incorrect.
[Thu Aug 22 22:08:45.150189 2019] [:error] [pid 13011:tid
140251715872896] NSS initialization failed. Certificate database:
/
William,
Thank you for your help.
There is something seriously wrong when importing certs and enabling ssl
in the admin console. I did a full fresh install of 389 and I get the
same error:
[Thu Aug 22 16:46:59.824914 2019] [:error] [pid 12634:tid
140387102636160] Password for slot internal
12 matches
Mail list logo
