Skip to content

Provisioning

The HCL Domino connector supports provisioning, allowing you to create and manage accounts and entitlements in HCL Domino directly from SailPoint.

Prerequisite: Your system is configured for provisioning.

When SailPoint provisions new accounts to the source, it uses the attributes on the Create Account page as instructions or a template for what to include in the account. This page is also referred to as the provisioning policy.

When new access is granted on a source where a user does not already have an account, SailPoint automatically includes account creation in the provisioning. This applies whether provisioning is started from an access request or from an automated role or lifecycle state assignment.

For direct-connect sources, SailPoint automatically creates the account from this configuration. If the source is not configured as a direct-connect source, SailPoint creates and assigns a provisioning task to the source owner and includes the values for the source owner to use in manually creating the account.

Important

This section describes the default Create Account configuration. SailPoint recommends that you work with Services to define a provisioning configuration specific to your company's needs. Be sure to verify large changes to the provisioning policy before implementation. Failure to do so might cause provisioning to fail.

Note

All paths are with respect to the Domino Server computer. For example, ID file path and mail file path. These paths must be accessible from the Domino Server computer.

Default Create Account Attributes

The following table lists the provisioning policy attributes for Create Accounts:

Note

All attributes should be of type 'String'. Attributes marked with an asterisk (*) are mandatory.

Account Attribute Generator Description
ServerName* Static The name of the server on which the account should be created.
CertifierIDfile Disable The ID file path of the certifier. For example, c:\id\cert.id
CertifierPassword Disable The password of the certifier ID file.
LastName* Static The last name of the user.
FullName* Static The full name of the user, using the following format: FirstName LastName/CertifierName
IDFilePath* Static The ID file path of the user. For example, c:\id\user.id
UserIDFilePassword* Static The ID file password of the user.
IDType* Static The type of the ID file. The following are the permissible values for the keyword: FLAT, HIERARCHICAL, CERTIFIER
UseCAProcess Static Specifies if CA process should be used at the time of user creation. Values: Y, N.
CertifierName Disable (Required if UseCAProcess attribute is enabled) Name of the certifier with the following format: /ABC/rootCert.

Update Policies

In update policies for account/group, the attribute names must be the same as their corresponding names in the document properties of account/group on Lotus Notes. To update the FullName of an account, the name of the attribute should be UserName.

No default value needs to be assigned for optional attributes if those do not need to be set.

The following lists the attributes for different update policies:

Note

Attributes marked with an asterisk (*) are mandatory.

Rename a User

Attribute Description
AC_Operation* The value of this attribute should be Rename User.
AC_certifierFilePath* The location of the Certifier ID file of the user. For example, c:\id\cert.id
AC_certifierPassword* The Certifier ID file password.
AC_lastName The new last name of the user.
AC_middleInitial The new middle name initial of the user.
AC_firstName The new first name of the user.
AC_orgUnit The new organizational unit of the user.
AC_altOrgUnit New alternate organizational unit of the user.
AC_altLanguage The new alternate language of the user.
AC_renameNotesUser* Determines whether you want to rename the Notes user or not. Values: True or False.

Recertify a User

Attribute Description
AC_Operation* The value of this attribute should be Recertify User.
AC_certifierFilePath* The location of the Certifier ID file of the user. For example, c:\id\cert.id
AC_certifierPassword* The Certifier ID file password.

Move a User

Attribute Description
AC_Operation* The value of this attribute should be Move User.
AC_currentCertifierFilePath* The location of the Certifier ID file of the user. For example, c:\id\cert.id
AC_currentCertifierPassword* The Certifier ID file password.
AC_targetCertifierFilePath* The location of the Certifier ID file of the user. For example, c:\id\target.id
AC_targetCertifierPassword* The Certifier ID file password.
AC_targetCertifierName* The name of the target certifier.

Change/Reset Password of a User

Attribute Description
HTTP_PASSWORD_CHANGE Must be set to Yes to change the HTTP (Internet) Password of a user. Values: Yes (default) and No.
IDFileCurrentPassword (Used only when the CURRENT_PASSWORD feature string is not present) The current password of the ID file.
IDFilePath The location where the user ID file is stored. For example, c:\id\user.id should be provided to change the ID file password of a user.
RESET_PASSWORD Must be set to Yes to reset the password of an ID file stored in the vault. Values: Yes and No (Default).

Sync ID File

Attribute Description
Operation* The value of this attribute should be Sync ID File.
IDFilePath* The location of the User ID file of the user. For example, c:\id\user.id
IDFilePassword* The User ID file password.

Get ID File

Attribute Description
Operation* The value of this attribute should be Get ID File.
IDFilePath* The location where the User ID file should be stored. For example, c:\id\user.id
IDFilePassword* The User ID file password.

Upload ID File

Attribute Description
Operation* The value of this attribute should be Upload ID File.
IDFilePath* The location where the User ID file is stored. For example, c:\id\user.id
IDFilePassword* The User ID file password.

Attach ID File to Mail File

Attribute Description
ATTACH_ID_TO_MAIL Specifies if the ID File should be attached to the Mail File or not. Values: Yes and No (Default).
MailServer The mail server of the user's mail file.
MailFile The mail file path. For example, mail\userMail.nsf

Documentation Feedback

Feedback is provided as an informational resource only and does not form part of SailPoint’s official product documentation. SailPoint does not warrant or make any guarantees about the feedback (including without limitation as to its accuracy, relevance, or reliability). All feedback is subject to the terms set forth at https://developer.sailpoint.com/discuss/tos.