22.12.2012 Views

Front cover - IBM Redbooks

Front cover - IBM Redbooks

Front cover - 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.

gets the user's Notes ID out of sync, which in the long run will cause lockout<br />

issues for the user.<br />

Since client-side warnings occur before the user accesses the server (for<br />

example, “Warning: Your password will expire on dd/mm/yy”) disabling password<br />

checking in the Server document will not suppress these warnings. It will,<br />

however, allow the Notes user ID to continue to gain access to the server even if<br />

the password has expired. To remove the warnings, the user should continue to<br />

change passwords at the frequency of the Last Change Date, Grace Period, and<br />

Expiration Date values stored in the ID.<br />

Note: Clearing the Last Change Date in the person document is not sufficient<br />

to unlock a user ID and allow them to log back into the server.<br />

Should the administrator need to lock a specific user out of the server, they can<br />

submit an adminp request to “Lockout the user.” When adminp processes the<br />

request the person document is modified so that the “Check Passwords” field is<br />

set to Lockout ID. When the user tries to access this server again they will<br />

receive an error message like the one shown in Figure 11-20.<br />

Figure 11-20 Authentication denied dialog box (user lockout)<br />

Throughout this example we have concentrated on a single server installation.<br />

With a multiple server install there are some “gotcha's” that may deny users<br />

access to certain servers. Since all the changes are made in the administration<br />

server’s names.nsf file, Domino relies on replication to ensure that other servers<br />

receive updates. Modifying a person document (for example, clearing the<br />

password digest) to reset a user account on one server will give the user back<br />

their access to all the other servers that have password checking enabled, but<br />

only after the Domino Directory has replicated the changes out.<br />

In pre-rollout testing, customers may experience behavior different to that<br />

documented here. The common problems are that adminp requests do not get<br />

processed before test results are recorded. It its also not recommended to test<br />

password checking with Grace Periods and Change Intervals of only 1 or 2 days.<br />

Before each step you should confirm that the pending adminp requests for the<br />

user being accepted are being processed. This also applies to production<br />

Chapter 11. Domino/Notes 6 security features 497

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

Saved successfully!

Ooh no, something went wrong!