Browsing Spanish translation

8.

<abbr title="Lightweight Directory Access Protocol">LDAP</abbr> is an advanced feature and if you've never heard of it then don't worry about this setting group.

27.

Advanced. Where in the LDAP hierarchy to search for groups. On Active Directory, this is usually 'cn=Builtin', otherwise it is often 'ou=Groups'. May be left blank (searches everywhere, based on object class).

28.

Advanced. Where in the LDAP hierarchy to search for members. On Active Directory, this is usually 'cn=Users', otherwise it is often 'ou=Users'. May be left blank (searches everywhere, based on object class).

29.

The property in LDAP used for logins. On Active Directory this is usually 'sAMAccountName', and on most Linux boxes it is 'uid' &ndash; but conceivably on some box 'cn' could work ('cn' is always there but often used for 'Full name' rather than the login name). Be aware that your choice of property isn't a true 'choice' (unless you check/tick the 'Manual authentication checks' option), what you specify must be in LDAP and must be what LDAP allows for its login ('bind') operations.

31.

The LDAP object class used to hold usergroups. On Active Directory, this is 'group'.

33.

The LDAP object class used to hold users. On Active Directory, this is 'user'.

37.

Advanced. Whether to check authentication via a password hash compare, as opposed to attempting an LDAP bind using the credentials. Doing a manual check divorces you from relying on LDAP to handle logins the way you want them, but also means you need LDAP to export password hashes in a standard format (Active Directory usually cannot).

40.

Enable/Disable Integrated Windows Kerberos Authentication for automatic desktop client logins.

62.

Whether to include the date-of-birth field for member accounts. It may be inappropriate to ask for a date of birth, or it may be vital for your market research, or you may want to provide a choice so that birthdays on your community may be celebrated.

64.

No date of births