SECURING
Setting up session-based name-and-password authentication is a multi-step process.
About this task
To set up single-server session-based name-and-password authentication for Web clients, you must complete three procedures.
1. Create a Web site document and enable it for session-based name-and-password authentication, or edit the Server document to require session authentication for Web clients.
2. Create a Person document for each user in the Domino® Directory on the Domino server and assign an Internet password to each user. It should be noted that users can be located instead in an external LDAP directory that is accessible to Domino through Directory Assistance.
3. Edit the database ACLs to give users access.
Parent topic: Session-based name-and-password authentication for Web clients
To enable single-server session-based authentication for Web Site documents
Procedure
1. From the Domino Administrator, click Configuration -> Web -> Internet Sites.
2. In the Internet Sites view, select the Web Site document for which you want to enable session authentication.
3. In the Web Site document, click Domino Web Engine and complete these fields.
5. Save the document.
To edit the Server document for single-server session-based name-and-password authentication
1. From the Domino Administrator, click Configuration, and open the Server document.
2. Click Internet Protocols -> Domino Web Engine.
3. Complete these fields:
5. Save and close the Server document.
To create Person documents for Web users
1. In the Domino Directory, create a Person document for each Web user who needs to access the server. (You can also edit the Person document of an existing user.)
2. In each Person document, complete these fields, and then save the document:
This field can contain multiple names. As Domino uses the first name in this field to validate a user in database ACLs, design access lists, groups, and File Protection documents, the first name in this field should be the user's Domino distinguished name (DN). The second name should be the common name (CN) portion of the DN.
For example, this field can contain these names:
Note: You should always use the user's hierarchical name -- for example, Alan Jones/Renovations/US -- to help eliminate ambiguous or duplicate user names.
After you edit the Server document and create Person documents, edit the database ACL of each database to which you want to give users access.
Related concepts Session-based name-and-password authentication for Web clients