22.12.2012 Views

Front cover - IBM Redbooks

Front cover - IBM Redbooks

Front cover - IBM Redbooks

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

same server/realm combination, it can reissue the request using the appropriate<br />

user ID and password.<br />

Some browsers go a step further and simply send a user ID and password for<br />

any URL that is likely to need it. Opera, Mozilla, Netscape Navigator and Internet<br />

Explorer all send the information with any URL that is in the same logical<br />

directory.<br />

The objective of these tricks is to reduce network traffic and improve<br />

responsiveness by eliminating a number of invalid requests and 401 status code<br />

responses. They also, unfortunately, have the undesired side effect of<br />

re-transmitting the user ID and password when it may not be necessary.<br />

However, there are ways to mitigate that. For each Internet protocol enabled on<br />

the server, it is possible to specify the method of security. For example, an<br />

Administrator might enable client certificate authentication for HTTP connections<br />

but require name-and-password security for LDAP connections that use TCP/IP.<br />

Or the Administrator might use name-and-password security with anonymous<br />

and SSL client authentication, for example, to allow users with SSL client<br />

certificates to authenticate using SSL client authentication and to allow other<br />

users to enter a name and password if they do not have an SSL client certificate.<br />

Note: Name-and-password authentication is not supported when a Domino<br />

server acts as an SMTP client – for example, when a Domino server connects<br />

to an SMTP server to route mail. Name-and-password security is supported<br />

only when a Domino server acts as an SMTP server, that is, when SMTP<br />

clients access a Domino server.<br />

It is possible to select the level of restriction Domino uses when authenticating<br />

users in Domino Directories and LDAP directories. This applies to all Internet<br />

protocols (HTTP, LDAP, IMAP, POP3). Using this setting makes servers less<br />

vulnerable to security attacks by refining how Domino searches for names and<br />

authenticates Internet clients. Domino also uses this setting when a Java applet<br />

hosted on a Domino server authenticates users with the Domino IIOP protocol.<br />

Fewer name variations with higher security<br />

The option “Fewer name variations with higher security” is the default setting and<br />

is recommended for tighter security. This authentication method is less<br />

vulnerable to attacks because a single authentication attempt does not produce<br />

as many matches, lessening the likelihood that a guessed password matches. It<br />

requires users to enter only the items listed in Table 6-2 on page 244 for the<br />

name-and-password dialog box in a Web browser or other Internet client.<br />

Chapter 6. Public key infrastructures 243

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

Saved successfully!

Ooh no, something went wrong!