Autobind should be enabled by default when creating instance with lib389 topologies

[389-ds-bot]

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

• Created at 2020-04-08 14:22:48 by bsmejkal
• Assigned to nobody

---

Issue Description

Ldapi autobind is not enabled when creating instance with lib389 topologies.
We have it enabled by default, if we create instance manually.

Steps to reproduce

1. Create instance using lib389 topology
2. Search for nsslapd-ldapi* attributes in cn=config

Actual results

nsslapd-ldapifilepath: /var/run/slapd-test.socket
nsslapd-ldapilisten: off
nsslapd-ldapiautobind: off
nsslapd-ldapimaprootdn: cn=Directory Manager
nsslapd-ldapimaptoentries: off
nsslapd-ldapiuidnumbertype: uidNumber
nsslapd-ldapigidnumbertype: gidNumber
nsslapd-ldapientrysearchbase: dc=example,dc=com

Expected results

Autobind should be enabled by default.

[389-ds-bot]

Comment from mreynolds (@mreynolds389) at 2020-04-08 15:05:39

As I mentioned in a PR - the problem is that lib389 topologies are still using the old installer(setup-ds.pl). We really need to get off of the legacy tools in lib389 especially since they are going way very soon!

[389-ds-bot]

Comment from mreynolds (@mreynolds389) at 2020-04-08 15:05:39

Metadata Update from @mreynolds389:

• Custom field origin adjusted to None
• Custom field reviewstatus adjusted to None

[389-ds-bot]

Comment from firstyear (@Firstyear) at 2020-04-09 00:49:17

They only use perl if you have compiled with perl because it reads from defaults.inf ....

[389-ds-bot]

Comment from mreynolds (@mreynolds389) at 2020-04-09 17:39:56

Metadata Update from @mreynolds389:

• Issue priority set to: normal
• Issue set to the milestone: 1.4.3

[mreynolds389]

This is for enabling ldapi when the old installer is used in 1.4.x. This is not needed in 2.x

[tbordaz]

old installer not evolving any more - new dscreate enables ldapi by default. CLosing this ticket. Please reopen if needed