Adam Pordzik wrote:
Hallvard B Furuseth wrote:
I'd note that the namespace pollution is nearly impossible to avoid
in any
reasonable manner. *ix users might be confused that it's rootdn/rootpw.
Note that people _also_ confuse rootdn with the suffix, since the suffix
is the root of the backend's tree (and is described as that some places,
though I don't remember where at the moment).
Me, I wouldn't mistake a directory manager (the fourth possibility :-) )
with neither unix nor windows admins. But "rootdn" is IMHO ambiguous
for the top of tree as Hallvard said.
Changing "rootdn" to something else might leads to more confusion with
existing documentation. However, "admindn" looks more handy to my eyes.
To effectively disambiguate the rootdn, the new name should exactly and
uniquely indicate its purpose. I'd not change it; as a second best
choice, I suggest using "databaseAdminDN". The "database" clarifies it
only refers to the database it's defined in.
p.
Ing. Pierangelo Masarati
OpenLDAP Core Team
SysNet s.n.c.
Via Dossi, 8 - 27100 Pavia - ITALIA
http://www.sys-net.it
------------------------------------------
Office: +39.02.23998309
Mobile: +39.333.4963172
Email: [EMAIL PROTECTED]
------------------------------------------
