Ldapi autobind is not enabled when creating instance with lib389 topologies. We have it enabled by default, if we create instance manually.
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
Autobind should be enabled by default.
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!
Metadata Update from @mreynolds: - Custom field origin adjusted to None - Custom field reviewstatus adjusted to None
They only use perl if you have compiled with perl because it reads from defaults.inf ....
Metadata Update from @mreynolds: - Issue priority set to: normal - Issue set to the milestone: 1.4.3
389-ds-base is moving from Pagure to Github. This means that new issues and pull requests will be accepted only in 389-ds-base's github repository.
This issue has been cloned to Github and is available here: - https://github.com/389ds/389-ds-base/issues/4072
If you want to receive further updates on the issue, please navigate to the github issue and click on subscribe button.
subscribe
Thank you for understanding. We apologize for all inconvenience.
Metadata Update from @spichugi: - Issue close_status updated to: wontfix - Issue status updated to: Closed (was: Open)
Login to comment on this ticket.