BaseDN and BindDN should reflect the real domain name with nethserver-directory

Development
1

I assume I don’t know if it is possible :wink: @davidep @giacomo

When you use nethserver-dc bindDN() and baseDN() reflect the real domain name with samba4 ldap, but when you use nethserver-directory, the template expand this

$servers->newServer('ldap_pla');

$servers->setValue('server','name','Openldap Server');
$servers->setValue('server','host',"127.0.0.1");
$servers->setValue('server','port',389);
$servers->setValue('login','auth_type','cookie');
$servers->setValue('login','bind_id',"cn=ldapservice,dc=directory,dc=nh");
$servers->setValue('login','bind_pass',"QUIBVTYKdZQsN5f2");
$servers->setValue('server','tls',true);
$servers->setValue('login','attr','uid');
$servers->setValue('server','base',array("dc=directory,dc=nh"));

hence

basedn = "dc=directory,dc=nh"
bindDN = "cn=ldapservice,dc=directory,dc=nh"

I know both are good, either the real domain name, or the generic domain directory.nh, but in phpldapadmin, it is not consistent, and if you display the real domain name it looks better.

2

The nethserver-directory configures an overlay DB with the real domain name. However I’d not use it for account management. The “dc=directory,dc=nh” is a well-known suffix I wouldn’t change.

3

ok, it was just to display the real domain name in phpldapadmin, not so important.

1 Like
4

I know it looks ugly, but it’s too convenient!

1 Like