Date: 2004-12-05T14:01:37 Editor: AlexKarasulu <[EMAIL PROTECTED]> Wiki: Apache Directory Project Wiki Page: EveGeneral URL: http://wiki.apache.org/directory/EveGeneral
no comment Change Log: ------------------------------------------------------------------------------ @@ -15,15 +15,8 @@ Requirements for Setting Admin (super-user) Password: * minimize setup overhead in general - * config-less operation even without providing a password should be possible for those - that just want to use eve as an LDAP backing store; in this case they effectively are - the super user and need to get around authorization issues to have free reign + * config-less operation even without providing a password should be possible for those that just want to use eve as an LDAP backing store; in this case they effectively are the super user and need to get around authorization issues to have free reign Notes: - * According to LDAP JNDI provider implementation guidelines, "if this property - [java.naming.security.authentication] is not set then its default value is none, unless - the java.naming.security.credentials property is set, in which case the default value is - simple." So this means config-less operation presumes anonymous binds and we must conform - to these guidelines. - * Most LDAP browsers do not allow simple binds using null or empty passwds. This makes - using a null password a poor choice for the super user. + * According to LDAP JNDI provider implementation guidelines, "if this property [java.naming.security.authentication] is not set then its default value is none, unless the java.naming.security.credentials property is set, in which case the default value is simple." So this means config-less operation presumes anonymous binds and we must conform to these guidelines. + * Most LDAP browsers do not allow simple binds using null or empty passwds. This makes using a null password a poor choice for the super user.
