Configuring the Alternate Scenario
This chapter describes how to configure the alternate smart card login scenario and add additional administrators to it.
Configuration Procedure
Configuring the alternate smart card login scenario consists of the following tasks:
-
Configuring the LDAP server on the DirX Identity Provisioning domain side for smart card login.
-
Configuring the Provisioning domain for smart card login.
-
Configuring the LDAP server on the Connectivity database side for smart card login.
-
Configuring the Connectivity database for smart card login from the Provisioning domain.
The next sections describe how to perform these tasks.
Prerequisites
The alternate scenario has the same prerequisites as the recommended scenario. See the section "Prerequisites" in the chapter "Configuring the Recommended Scenario".
Configure the LDAP Server - Provisioning
To configure the LDAP server on the Provisioning domain side for smart card login, follow the steps given in "Configuring the DSA and LDAP Server".
Configure DirX Identity - Provisioning
To configure the DirX Identity Provisioning domain for smart card login:
-
Create the personalized DomainAdmin as described in the chapter "Creating a Personalized DomainAdmin".
-
Store the smart card certificate in this personalized DomainAdmin as described in the section "Store the Smart Card Certificate in the Personalized DomainAdmin".
-
In the Provisioning → Users view, create a mirror of the personalized DomainAdmin object you just created - for example, MyMirrorAdmin - to hold the encrypted password (dxmPassword attribute). This user object only needs to hold the encrypted password; no group assignments are necessary.
-
Change to the Data View and then edit the userpassword field of your mirror personalized DomainAdmin user object to set the password.
-
In the Provisioning → Users view, link the personalized DomainAdmin user object to the mirror personalized DomainAdmin user object using the Mirrored User field in the SASL external bind section of the Authentication tab of the personalized DomainAdmin user.
-
Change to Data View → Connectivity.
-
Create the mirrored user for the personalized DomainAdmin - for example, Mirrored MyDomainAdmin - with the same password as the mirror personalized DomainAdmin you previously created in the Provisioning view (for example, MyMirrorAdmin). See step 7 in the chapter "Creating a Personalized DomainAdmin".
-
In Data View → Connectivity, add the mirrored user for the personalized domainAdmin - for example, Mirrored MyDomainAdmin - to the DirXmetahub read and write groups as described in "Add the Personalized DomainAdmin to DirXmetahub Read and Write Groups".
-
Ensure that the DirX Identity Manager runtime uses the Java 11 JRE (64 bit) as described in "Configure Java 11 JRE (64-bit)".
-
Set up the login profile for Provisioning as described in "Set up the Login Profiles".
-
Set up SASL authentication to the request workflow service as described in "Set up Request Workflow Service SASL Authentication".
Configure the LDAP Server - Connectivity
To configure the LDAP server for the DirX Identity Connectivity database, follow the steps given in "Configuring the DSA and LDAP Server".
Configure DirX Identity - Connectivity
To configure the DirX Identity Connectivity database for smart card login:
-
In DirX Identity Manager’s Data View → Connectivity:
-
Create a personalized DomainAdmin for smart card login to the Connectivity side - for example, MyMetahubAdmin - and then store the smart card certificate in the userCertificate attribute for this use. This user must have the inetOrgPerson object class, because this object class contains the userCertificate attribute. To create this user, right-click in the cn=Users tree and then select New → Internet Organizational Person.
-
Add this personalized DomainAdmin to the DirXmetahub read and write groups as described in "Add the Personalized DomainAdmin to DirXmetahub Read and Write Groups".
-
Ensure that the DirX Identity Manager runtime uses Java 11 JRE (64-bit) as described in the section "Configure Java 11 JRE (64-bit)".
-
Set up the login profile for Connectivity as described in "Set up the Login Profiles".
Enabling Additional Administrators - Alternate Scenario
If you have already set up the smart card login for one administrator, you can define additional administrators by performing a subset of the configuration tasks. The next sections describe this subset.
Configure the LDAP Servers - Provisioning and Connectivity
In the LDAP Configuration subentry for both LDAP servers, add the distinguished name of the new personalized DomainAdmin to the LDAP Extended Operations Read Users attribute (or use the value all) to allow the new personalized DomainAdmin to perform all extended LDAP read operations. See the section "Configuring the DSA and LDAP Server" for details.
Configure DirX Identity - Provisioning
To add new personalized DomainAdmins to the Provisioning side:
-
Create the new personalized DomainAdmin as described in the chapter "Creating a Personalized DomainAdmin".
-
Store the smart card certificate in this new personalized DomainAdmin as described in the section "Store the Smart Card Certificate in the Personalized DomainAdmin".
-
In the Provisioning → Users view, create a mirror personalized DomainAdmin user object for the new personalized DomainAdmin to hold the encrypted password.
-
Change to the Data View and then set this password (edit the mirrored user object’s userpassword attribute).
-
In the new personalized DomainAdmin, use the Mirrored User field (Provisioning → Users → new personalized DomainAdmin → Authentication tab → SASL external bind section) to link the mirror personalized DomainAdmin to the new personalized DomainAdmin.
-
Change to Data View → Connectivity. In this view, create another mirrored user for the personalized DomainAdmin with the same password as the mirror personalized DomainAdmin you created in the Provisioning view and then add it to the DirXmetahub read and write groups (See step 7 in the chapter "Creating a Personalized DomainAdmin").
-
Set up the login profile for Provisioning as described in the section "Set up the Login Profiles".