General.CACertificate inf directive does not work.

[389-ds-bot]

Cloned from Pagure issue: https://pagure.io/389-ds-base/issue/47390

• Created at 2013-06-15 23:10:25 by jvukotic
• Closed as Invalid
• Assigned to nobody

---

The ticket apply to setup-ds-admin.pl script for 389 Directory Server version 1.2.11.15.
When included in inf file that is supplied as a -f argument of setup-ds-admin.pl script, neither the CA certificate gets imported in admin server's cert8.db, nor adm.conf is modified with the supplied ldaps url, also listed in the submitted inf file as a General.ConfigDirectoryLdapURL argument value.

[389-ds-bot]

Comment from rmeggins (@richm) at 2013-08-20 04:11:26

Replying to [ticket:47390 jvukotic]:

The ticket apply to setup-ds-admin.pl script for 389 Directory Server version 1.2.11.15.
When included in inf file that is supplied as a -f argument of setup-ds-admin.pl script, neither the CA certificate gets imported in admin server's cert8.db, nor adm.conf is modified with the supplied ldaps url, also listed in the submitted inf file as a General.ConfigDirectoryLdapURL argument value.

Can you tell me if these are the right steps to reproduce the problem?

1. setup a brand new 389 instance - set it up to use SSL - export the CA cert to a file
2. setup another brand new 389 instance - configure it to use the first instance as the ConfigDS

[389-ds-bot]

Comment from rmeggins (@richm) at 2013-10-03 03:02:49

Replying to [comment:3 richm]:

Replying to [ticket:47390 jvukotic]:

The ticket apply to setup-ds-admin.pl script for 389 Directory Server version 1.2.11.15.
When included in inf file that is supplied as a -f argument of setup-ds-admin.pl script, neither the CA certificate gets imported in admin server's cert8.db, nor adm.conf is modified with the supplied ldaps url, also listed in the submitted inf file as a General.ConfigDirectoryLdapURL argument value.

Can you tell me if these are the right steps to reproduce the problem?

1. setup a brand new 389 instance - set it up to use SSL - export the CA cert to a file
2. setup another brand new 389 instance - configure it to use the first instance as the ConfigDS

Still waiting for a reply - please respond.

[389-ds-bot]

Comment from rmeggins (@richm) at 2013-10-06 08:04:59

Steps:

1. Setup 389-ds-base 1.3.1 and 389-admin (latest) - set up for SSL - use ldaps as the config ds url
2. Install 389-ds-base 1.2.11 and 389-admin (latest) - run setup-ds-admin.pl on a different host to install a new admin server and ds instance, using ldaps as the config ds url and a ca cert file

• ca cert is installed correctly in admin server cert8.db
• ca cert is not installed in directory server cert8.db - this is by design, not a bug

[389-ds-bot]

Comment from rmeggins (@richm) at 2017-02-11 22:53:20

Metadata Update from @richm:

• Issue set to the milestone: 389-admin,console 1.1.36