Re: Using sec-activate to enable SSL for admin server

[Mark Reynolds <mreynolds@xxxxxxxxxx>]

On 11/6/19 12:42 AM, Grant Byers wrote:

Hi,

 

I’ve mostly completed automated deployment of a 389ds cluster via Ansible. The final piece of the puzzle is the enablement of SSL/TLS for the Admin server.  From what I understand, I should be able to use the sec-activate tool to do this;

 

/usr/lib64/dirsrv/cgi-bin/sec-activate /etc/dirsrv/admin-serv on

 

What I can’t figure out is how to authenticate. When I run this, it prompts me repeatedly for Ënter Admin Server Administrator password:”. I have tried both the RootDN and ConfigDirectoryAdminPwd passwords, but neither seem to work.

 

Can anyone suggest what’s going on here & how I might get past it?

 

I have never used, or heard of anyone using, sec-activate to enable SSL in the admin server.  I suggest following the official documentation on setting this up using certutil and a password/pin file:

https://access.redhat.com/documentation/en-us/red_hat_directory_server/10/html/administration_guide/enabling_tls#enabling_tls_in_the_administration_server

HTH,

Mark

Thanks,

Grant

_______________________________________________
389-users mailing list -- 389-users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to 389-users-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/389-users@xxxxxxxxxxxxxxxxxxxxxxx

-- 

389 Directory Server Development Team
  

_______________________________________________
389-users mailing list -- 389-users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to 389-users-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/389-users@xxxxxxxxxxxxxxxxxxxxxxx