25.02.2013 Views

TCP/IP Tutorial and Technical Overview - IBM Redbooks

TCP/IP Tutorial and Technical Overview - IBM Redbooks

TCP/IP Tutorial and Technical Overview - IBM Redbooks

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

472 <strong>TCP</strong>/<strong>IP</strong> <strong>Tutorial</strong> <strong>and</strong> <strong>Technical</strong> <strong>Overview</strong><br />

built-in mechanisms to allow the use of the<br />

platform-specific controls.<br />

Because the use of authorization controls is platform-specific, the following<br />

sections describe only the authentication, integrity, <strong>and</strong> confidentiality. There are<br />

several mechanisms that can be used for this purpose; the most important ones<br />

are discussed here. These are:<br />

► No authentication<br />

► Basic authentication<br />

► Simple Authentication <strong>and</strong> Security Layer (SASL)<br />

► Transport Layer Security (TLS)<br />

The security mechanism to be used in LDAP is negotiated when the connection<br />

between the client <strong>and</strong> the server is established.<br />

No authentication<br />

No authentication should only be used when data security is not an issue <strong>and</strong><br />

when no special access control permissions are involved. This might be the<br />

case, for example, when your directory is an address book browsable by<br />

anybody. No authentication is assumed when you leave the password <strong>and</strong> DN<br />

field empty in the bind API call. The LDAP server then automatically assumes an<br />

anonymous user session <strong>and</strong> grants access with the appropriate access controls<br />

defined for this kind of access (not to be confused with the SASL anonymous<br />

user discussed in “Simple Authentication <strong>and</strong> Security Layer (SASL)”).<br />

Basic authentication<br />

Basic authentication is also used in several other Web-related protocols, such as<br />

HTTP. When using basic authentication with LDAP, the client identifies itself to<br />

the server by means of a DN <strong>and</strong> a password, which are sent in the clear over<br />

the network (some implementations might use Base64 encoding instead). The<br />

server considers the client authenticated if the DN <strong>and</strong> password sent by the<br />

client matches the password for that DN stored in the directory. Base64 encoding<br />

is defined in the Multipurpose Internet Mail Extensions, or MIME (see 15.3,<br />

“Multipurpose Internet Mail Extensions (MIME)” on page 571). Base64 is a<br />

relatively simple encryption, <strong>and</strong> it is not hard to break after the data has been<br />

captured in the network.<br />

Simple Authentication <strong>and</strong> Security Layer (SASL)<br />

SASL is a framework for adding additional authentication mechanisms to<br />

connection-oriented protocols, <strong>and</strong> is defined in RFC 4422. It has been added to<br />

LDAPv3 to overcome the authentication shortcomings of Version 2. SASL was<br />

originally devised to add stronger authentication to the IMAP protocol (see 15.5,

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!