HCLSoftware Business Partner
Domino Consulting Services
CRUCIAL Notes Tools
+1 212-599-2048

Domino Consulting Services
CRUCIAL Notes Tools
Domino administration
Notes development

Facebook Twitter YouTube
Chat now       
.
ProductsDownloadsNewsAbout usContact


Need a Domino Consultant? Call NotesMail +1 212-599-2048 - HCLSoftware Business Partner

SECURING

Configuring user name mapping when you manage Domino users through Active Directory

Follow the steps in this topic to configure user name mapping for a Windows™ single sign-on environment if you manage HCL Domino® user information primarily through Active Directory. This configuration requires you to add users' HCL Notes® distinguished names to Active Directory user accounts.

Procedure

1. In a directory assistance database, create an LDAP directory assistance document to use to connect to the Active Directory server.


    Table 1. Important Fields in an LDAP Directory Assistance Document
    TabFieldValueComment
    BasicsMake this domain available toNotes clients and Internet Authentication/Authorization
    • Required
    • LDAP Clients is optional
    BasicsGroup AuthorizationYes or NoSelect Yes if you want to use Active Directory groups in database ACLs.
    BasicsAttribute to be used as name in an SSO token$DN
    • Required only if there is an IBM® WebSphere® SSO server authenticating users against Active Directory so that users' LTPA tokens contain their Active Directory names.
    • Requires Map names in LTPA token to be enabled in the Web SSO Configuration document.
    • Ensures proper SSO operation for servers that authenticate users against Active Directory.
    Basics - SSO configurationWindows single sign-on for Web clientsEnabledEnables efficient name lookups based on users' Active Directory logon (Kerberos) names. In combination with Attribute to be used as Notes Distinguished Name, allows the user's Kerberos identity to be associated with the Domino name.
    Basics - SSO configurationKerberos realmActive Directory domain Specify in uppercase characters, for example, AD.RENOVATIONS.COM.
    Naming Contexts (Rules)Trusted for CredentialsYes
    LDAPAttribute to be used as Notes Distinguished Nameattribute
    • Attribute in Active Directory that stores users' Notes distinguished names.
    • A directory administrator may need to extend the Active Directory schema to add an attribute for this name if there is no existing attribute that already contains the Notes distinguished name. Alternatively it may be feasible to use the altSecurityIdentities attribute, if not already in use for another purpose.
    • A directory synchronization tool such asIBM Tivoli® Directory Integrator can be used to populate the attribute with the Notes names.
    • The value stored in the attribute must adhere to valid distinguished name syntax. In Active Directory use LDAP comma (,) separators in the Notes names rather than the Notes forward slash (/) separators; for example:

      cn=Betty Zechman,ou=Marketing,o=Renovations


    rather than

      cn=Betty Zechman/ou=Marketing/o=Renovations
    • Used to link this Active Directory record to a Notes distinguished name for determining user access to Domino resources.
    LDAPType of search filter to useActive Directory
2. If users have Person documents in the Domino Directory, make the following edits to them. Person documents are optional for Web users who are not HCL iNotes® users.

    Table 2. Edits Needed in Person Documents
    TabFieldValueComment
    BasicsInternet Password

    (HTTPPassword)

    None (recommended)

    Or

    password-hash

    • If desired, remove the password to use user's Active Directory passwords for Internet access that requires user password verification.
    • When password removed, set directory access to prevent users from adding passwords themselves.
    • When password removed, Domino verifies user passwords in Active Directory in situations when Windows single sign-on is not available.


3. If users have Domino Person documents but you do not include their Domino Internet passwords in them, disable the following Internet password settings in users' effective Security Settings policy document:

    Table 3. Settings to Disable in Users' Effective Security Settings Policy Document
    TabFieldValueComment
    Password Management BasicsAllow Users to Change Internet Password over HTTPNoThe default behavior is Yes. If there is no Security Settings policy document specified for users, create one in order to change the default behavior.
    Password Management BasicsUpdate Internet Password When Notes client Password ChangesNo
    Password Management BasicsEnforce Password ExpirationDisabled or Notes Only
4. On the Security -> Internet Access tab of the Server documents of participating Domino servers, for Internet authentication, select Fewer name variations with higher security.

5. If some SSO servers are authenticating users against Active Directory, specify the following setting in the Web SSO Configuration document:


    Table 4. Web SSO Configuration Settings
    TabFieldValueComment
    Basics - Token ConfigurationMap names in LTPA tokensEnabled
    • Used to map Active Directory distinguished names in SSO LTPA tokens to Notes distinguished names for determining user access to Domino resources.
    • Used to ensure functioning SSO at servers that authenticate the user against Active Directory.


Parent topic: Configuring user name mapping in a Windows single sign-on for Web clients environment

Related concepts
Configuring user name mapping in a Windows single sign-on for Web clients environment
Access levels in the ACL

Related tasks
Creating a Directory Assistance document for a remote LDAP directory
Creating a security policy settings document
Creating a Web SSO configuration document

Related information
Troubleshooting Windows single sign-on for Web clients (SPNEGO)