[389-users] Scripting SSL Enabling of 389-DS Admin Serv and Instances

[Paul Whitney]

I have been building 389DS directory serves, and can automate most of the installation
process to include creating my instances such as config.  However, SSL enabling seems to
be difficult. I tried the simple copy db files and pin.txt, but when I get into the
console to enable the certs, there seems to be a problem opening the DB files and
selecting the certificate to use for SSL.



If I go through the console, select Manage certificates, enter a new password, import a CA
cert, then replace the DB files with the ones from an existing server, it works. 



Is there something special that needs to be done to "initialize" the new DB
files that can be scripted (ansible) that will set the password for the new server, then
copy the DB files/pin.txt.?

Thanks,

Paul M. Whitney
E-mail: paul.whitney(a)mac.com
Sent from my browser.