Configuring LDAP Services for Novell eDirectory
351
no
vd
ocx (
E
NU)
01
F
ebr
ua
ry
200
6
4
(Optional) Assign the proxy user rights to specified directories.
5
Click
LDAP
>
LDAP Overview
>
View LDAP Groups
> the LDAP Group object.
6
In the
Proxy User
field, click the
Browse
button, browse to and select the LDAPProxy user,
then click
OK
.
13.6.9 Using SASL
Simple Authentication and Security Layer (SASL) defines various authentication mechanisms that
must be registered with the Internet Assigned Numbers Authority (IANA). The LDAP server
supports the following mechanisms:
•
DIGEST-MD5
•
EXTERNAL
•
NMAS_LOGIN
•
GSSAPI
These mechanisms are installed on the server during an eDirectory installation or upgrade. However,
on Linux and UNIX, you have to run the nmasinst utility to install NMAS methods.
The LDAP server queries SASL for the installed mechanisms when it gets its configuration, and
automatically supports whatever is installed. The LDAP server also reports the current supported
SASL mechanisms in its rootDSE by using the supportedSASLMechanisms attribute.
Because these mechanisms are registered, you must enter them using all uppercase characters.
Otherwise, the LDAP server won't recognize them.
The LDAP bind protocol allows the client to use various SASL mechanisms for authentication.
When the application uses the LDAP bind API, it would either need to choose the simple bind and
supply a DN and password, or choose the SASL bind and supply the SASL mechanism name in
upper case, and any associated SASL credentials required by the mechanism.
DIGEST-MD5
The DIGEST-MD5 mechanism does not require TLS. The LDAP server supports DIGEST-MD5
over clear and secure connections.
LDAP supports SASL mechanisms in the bind request. Instead of requesting an LDAP simple bind
(DN and clear-text password), you request an LDAP SASL bind. This request provides a DN and
MD5 credentials.
MD5 provides an encrypted hash of passwords. Passwords are encrypted even on clear connections.
Therefore, the LDAP server accepts passwords that use MD5 on either the clear-text or encrypted
port.
If someone sniffs this connection, the password can't be detected. However, the entire connection
can be spoofed or hijacked.
This mechanism is an LDAP SASL bind (and not a simple bind). Therefore, the LDAP server
accepts these requests, even if you checked the
Require TLS for Simple Binds with Passwords
check
box during installation.
Содержание EDIRECTORY 8.8 - GUIDE
Страница 4: ...novdocx ENU 01 February 2006...
Страница 16: ...16 Novell eDirectory 8 8 Administration Guide novdocx ENU 01 February 2006...
Страница 68: ...68 Novell eDirectory 8 8 Administration Guide novdocx ENU 01 February 2006...
Страница 90: ...90 Novell eDirectory 8 8 Administration Guide novdocx ENU 01 February 2006...
Страница 116: ...116 Novell eDirectory 8 8 Administration Guide novdocx ENU 01 February 2006...
Страница 128: ...128 Novell eDirectory 8 8 Administration Guide novdocx ENU 01 February 2006...
Страница 184: ...184 Novell eDirectory 8 8 Administration Guide novdocx ENU 01 February 2006...
Страница 249: ...250 Novell eDirectory 8 8 Administration Guide novdocx ENU 01 February 2006...
Страница 307: ...308 Novell eDirectory 8 8 Administration Guide novdocx ENU 01 February 2006...
Страница 333: ...334 Novell eDirectory 8 8 Administration Guide novdocx ENU 01 February 2006...
Страница 371: ...372 Novell eDirectory 8 8 Administration Guide novdocx ENU 01 February 2006...
Страница 439: ...440 Novell eDirectory 8 8 Administration Guide novdocx ENU 01 February 2006...
Страница 519: ...520 Novell eDirectory 8 8 Administration Guide novdocx ENU 01 February 2006...
Страница 529: ...530 Novell eDirectory 8 8 Administration Guide novdocx ENU 01 February 2006...
Страница 555: ...556 Novell eDirectory 8 8 Administration Guide novdocx ENU 01 February 2006...