This topic describes how to configure IdentityForge for use with EmpowerID. Once you have followed the steps outlined in this topic, you can connect EmpowerID to your AS/400 directories.

To install the Java environment

Execute the Java JDK installer and click Next.
On the optional features page, click the Source Code button and select This feature will not be available.
Click Development Tools and then click the Change button.
Change C:\Program Files\Java\jdk-11.0.1\ to a shorter path without spaces in it, such as C:\software\jdk-11.0.1\, and click OK.
Click Next to begin the installation and click Close when it finishes.

To configure the Java environment

From the Start menu, type "Control" and press ENTER to open Control Panel.
In Control Panel, search for "Environment" and under System, click the link for Edit environment variables for your account.
In the System variables pane of the Environment Variables window that appears, click New.
In the New System Variable dialog that appears, type the following values and click OK.
1. Variable name: JAVA_HOME
2. Variable value: installation path of the Java JDK, e.g. C:\software\jdk-11.0.1\
Close the Environment Variables window and then close Control Panel.
From the downloads mentioned as prerequisites above, extract i5_advanced_adapter_5.0.0.4_enterprise.zip to the root of the partition (C:\ in our example).
1. Navigate to the C:\i5_Advanced_Adapter_5.0.0.4_Enterprise\etc\LDAP Gateway folder.
2. Extract ldapgateway.zip to the root of the partition (C:\ in our example).
From the downloads, extract jtopen_9_6.zip to a folder named jtopen_9_6 in the root of the partition (C:\ in our example).
1. Navigate to the C:\jtopen_9_6\lib folder.
2. Copy jt400.jar and util400.jar and paste them in the C:\ldapgateway\lib folder.
Navigate to C:\ldapgateway\bin and open run.bat in the text editor of your choice.
1. Adjust the following line to the installation path of the Java JDK:
```
set JAVA_HOME=\software\jdk1.7.0_01
```
  In our example, we change this line to the following:
```
set JAVA_HOME=C:\software\jdk-11.0.1
```
2. Save and close the file.

To configure the IdentityForge as400.properties file

Navigate to the C:\ldapgateway\conf folder and open the as400.properties file in the text editor of your choice.
In the text editor, change the following parameter to true:
```
_isSSL_
```
Adjust the following parameters with the IP address of your target iSeries:
```
_host_ 
_agentHost_
```
Adjust the following parameters with the UID of the administrative AS/400 account:
```
_adminId_            
_agentAdminId_
```
Place a '#' in front of the following parameters to comment them out:
```
_adminPwd_           
_agentAdminPwd_
```
Remove the '#' from the following parameters to uncomment them:
```
_adminPwdEncrypt_            
_agentAdminPwdEncrypt_
```
Save the file and leave it open for the encrypted hex values.

To encrypt hex values for the passwords

Navigate to the C:\i5_Advanced_Adapter_5.0.0.4_Enterprise\scripts folder and copy the propertyEncrypt.bat file.
Paste the file in the C:\ldapgateway\dist folder, and then open the file in the text editor of your choice.
Adjust the following line to the installation path of the Java JDK:
```
set JAVA_HOME=C:\software\jdk1.5.0_15
```
In our example, this line is:
```
set JAVA_HOME=C:\software\jdk-11.0.1
```
Scroll through the propertyEncrypt.bat file until you see the following line:
```
SET CLASSPATH=C:\software\identityforge\ldapgateway\dist\idfserver.jar
```
Change this path to point to the IdentityForge installation directory. In our example, this line is:
```
SET CLASSPATH=C:\ldapgateway\dist\idfserver.jar
```

Scroll to the end of the propertyEncrypt.bat file until you see the following lines:

rem Start Property Encrypt Utility 
%JAVACMD%  %JVM_OPTS%  -cp %CLASSPATH%  com.identityforge.idfserver.util.AESCipherUtil idfRacfPwd

Change idfRacfPwd to the password of the AS/400 administrative account, then close and save the file.
Double-click propertyEncrypt.bat to see output similar to the following:
```
New encrypted string as HEX: 10902AA71C4DF819C965E8B5B7DF0208
```
Copy the hex value (in our example, 10902AA71C4DF819C965E8B5B7DF0208) to the clipboard.
Navigate to the C:\ldapgateway\conf folder and open the as400.properties file in the text editor of your choice.
Paste the hex value into the following parameters:
```
_adminPwdEncrypt_
_agentAdminPwdEncrypt_
```

To unpack the IdentityForge environment

Navigate to C:\ldapgateway\dist and rename idfserver.jar to idfserver.zip.
Extract the contents of idfserver.zip to C:\ldapgateway\dist\idfserver.

To configure the Front-End LDAP Administrative Account

The next step is to set the Front-End LDAP administrative account and password. This is the account used by EmpowerID to bind to the IdentityForge LDAP server.

Open C:\ldapgateway\dist\idfserver\beans.xml in the text editor of you choice and scroll to the as400 section. We will change the value for the Front-End LDAP administrative account adminUserDN and altAdminUserDN.

<bean name="as400" singleton="true" class="com.identityforge.idfserver.backend.as400.As400Module">

<property name="suffix" value="dc=as400,dc=com"/>    
<property name="workingDirectory" value="../as400"/>    
<property name="adminUserDN" value="cn=idfAs400Admin, dc=as400,dc=com"/>     
<property name="adminUserPassword" value="idfAs400Pwd"/>    
<property name="altAdminUserDN" value="cn=oimAs400Admin, dc=as400,dc=com"/>    
<property name="altAdminUserPassword" value="oimAs400Pwd"/>    
<property name="allowAnonymous" value="false"/>    
<property name="entryCacheSize" value="1000"/>    
<property name="defaultUacc" value="read"/>    
<property name="searchUsersType" value="user"/>

IdentityForge allows two Front-End LDAP administrative accounts, but for our purposes we only need one.

Change the adminUserDN and altAdminUserDN property values to the DN of the Front-End account you wish to use to bind to LDAP. For example:

<bean name="as400" singleton="true" class="com.identityforge.idfserver.backend.as400.As400Module">

<property name="suffix" value="dc=as400,dc=com"/>    
<property name="workingDirectory" value="../as400"/>   
<property name="adminUserDN" value="cn=EIDIDF, dc=as400,dc=com"/>    
<property name="adminUserPassword" value="idfAs400Pwd"/>   
<property name="altAdminUserDN" value="cn=EIDIDF, dc=as400,dc=com"/>   
<property name="altAdminUserPassword" value="oimAs400Pwd"/>    
<property name="allowAnonymous" value="false"/>    
<property name="entryCacheSize" value="1000"/>    
<property name="defaultUacc" value="read"/>    
<property name="searchUsersType" value="user"/>

Open C:\ldapgateway\dist\propertyEncrypt.bat in the text editor of your choice.

Scroll to the end of the propertyEncrypt.bat file until you see the following lines:

rem Start Property Encrypt Utility
%JAVACMD%  %JVM_OPTS%  -cp %CLASSPATH%  com.identityforge.idfserver.util.AESCipherUtil idfRacfPwd

Change idfRacfPwd to the password of the Front-End LDAP administrative account and then save the propertyEncrypt.bat file.
Double-click propertyEncrypt.bat to see output similar to the following:
```
New encrypted string as HEX: 10902AA71C4DF819C965E8B5B7DF0208
```
Copy the value (in our example, 10902AA71C4DF819C965E8B5B7DF0208) to the clipboard.

Change the adminUserPassword and altAdminUserPassword property values to the encrypted password string in the clipboard. For example:

<bean name="as400" singleton="true" class="com.identityforge.idfserver.backend.as400.As400Module">

<property name="suffix" value="dc=as400,dc=com"/>    
<property name="workingDirectory" value="../as400"/>    
<property name="adminUserDN" value="cn=EIDIDF, dc=as400,dc=com"/>   
<property name="adminUserPassword" value="10902AA71C4DF819C965E8B5B7DF0208â/>    
<property name="altAdminUserDN" value="cn=EIDIDF, dc=as400,dc=com"/>    
<property name="altAdminUserPassword" value="10902AA71C4DF819C965E8B5B7DF0208"/>    
<property name="allowAnonymous" value="false"/>    
<property name="entryCacheSize" value="1000"/>    
<property name="defaultUacc" value="read"/>    
<property name="searchUsersType" value="user"/>

To configure the Back-End LDAP Administrative Account

The next step is to set the Back-End LDAP administrative password. This is the account used by EmpowerID to bind to the IdentityForge LDAP server and sync inventory to the Back-End.

Open C:\ldapgateway\dist\idfserver\beans.xml in the text editor of your choice.

Scroll to the section shown below. We will change the Back-End LDAP administrative account password for adminUserPassword and altAdminUserPassword:

<bean name="hpbe2" singleton="true" class="com.identityforge.idfserver.backend.hpbe.HPBEModule">
<property name="suffix" value="dc=system,dc=backend"/>
<property name="workingDirectory" value="../system"/>
<property name="schema" ref="schemas"/>
<property name="adminUserDN" value="cn=Directory Manager, dc=system,dc=backend"/>
<property name="adminUserPassword" value="testpass"/>
<property name="altAdminUserDN" value="cn=Directory Manager, dc=system,dc=backend"/>
<property name="altAdminUserPassword" value="testpass"/>
<property name="entryCacheSize" value="1000"/>

Open C:\ldapgateway\dist\propertyEncrypt.bat in the text editor of your choice.

Scroll to the end of the propertyEncrypt.bat file until you see the following lines:

rem Start Property Encrypt Utility
%JAVACMD%  %JVM_OPTS%  -cp %CLASSPATH%  com.identityforge.idfserver.util.AESCipherUtil idfRacfPwd

Change idfRacfPwd to the password of the Back-End LDAP administrative account and then save the propertyEncrypt.bat file.
Double-click propertyEncrypt.bat to see output similar to the following:
```
New encrypted string as HEX: 10902AA71C4DF819C965E8B5B7DF0208
```
Copy the value (in our example, 10902AA71C4DF819C965E8B5B7DF0208) to the clipboard.

Change the adminUserPassword and altAdminUserPassword property values to the encrypted password string in the clipboard. For example:

<bean name="hpbe2" singleton="true" class="com.identityforge.idfserver.backend.hpbe.HPBEModule">
<property name="suffix" value="dc=system,dc=backend"/>
<property name="workingDirectory" value="../system"/>
<property name="schema" ref="schemas"/>
<property name="adminUserDN" value="cn=Directory Manager, dc=system,dc=backend"/>
<property name="adminUserPassword" value="10902AA71C4DF819C965E8B5B7DF0208"/>
<property name="altAdminUserDN" value="cn=Directory Manager, dc=system,dc=backend"/>
<property name="altAdminUserPassword" value="10902AA71C4DF819C965E8B5B7DF0208"/>
<property name="entryCacheSize" value="1000"/>

To configure SSL for the IdentityForge LDAP server

To configure secure communications between EmpowerID and the IdentityForge LDAP server we need a PFX copy of the certificate being used by EmpowerID and an installed copy of OpenSSL to convert the PFX to a format usable by Java keystores.

Install the Microsoft Visual C++ 2008 Redistributable Package (x86) by running vcredist_x86.exe.
Next, install Win32 OpenSSL v1.0.2p Light by running Win32OpenSSL_Light-1_0_2p.exe. In our example, the installation path is C:\software\OpenSSL-Win32.
1. Click Next. When prompted where to copy the OpenSSL DLLs, choose The OpenSSL binaries (/bin) directory.
2. Click Next and finish the installation.
Copy the PFX certificate (named EIDcert.pfx in our example) to the root of the partition (C:\ in our example).
Open a Command Prompt window and navigate to C:\software\OpenSSL-Win32\bin.
1. Execute the following command to convert the PFX file to a PEM file.
```
openssl pkcs12 -in C:\EIDcert.pfx -out C:\EIDcert.pem
```
  The OpenSSL toolkit asks you to enter the import password; this is the pass phrase currently set on the PFX certificate. If you exported the certificate from the MMC snap-in, this is the password you set on the certificate during the export.
2. Enter the password for the certificate and press ENTER.
3. OpenSSL prompts for the PEM pass phrase. Enter the pass phrase and press ENTER, then enter the pass phrase again to confirm and press ENTER once more.
  
  We are setting a new pass phrase here--be sure to remember this value! You can use the same password as the import password if you prefer.
  
  We now have a PEM file available at C:\EIDcert.pem.
Using the text editor of your choice, open the PEM file (C:\EIDcert.pem in our example) so that we can extract the private key and place it in a separate file.
1. Find the following lines:
```
-----BEGIN ENCRYPTED PRIVATE KEY-----
            DATA HERE
-----END ENCRYPTED PRIVATE KEY-----
    
```
2. Copy everything from the beginning of the -----BEGIN ENCRYPTED PRIVATE KEY----- line to the end of the -----END ENCRYPTED PRIVATE KEY----- line and paste them into a new text file named C:\encrypted.pem. Make sure there are no extra line breaks or spaces at the beginning or end of the file.
3. To pull out the public key and put it into a separate file, find the following lines:
```
-----BEGIN CERTIFICATE-----
        DATA HERE
-----END CERTIFICATE-----
    
```
4. Copy everything from the beginning of the -----BEGIN CERTIFICATE----- line to the end of the -----END CERTIFICATE----- line and paste them into a new text file named C:\cert.pem. Make sure there are no extra line breaks or spaces at the beginning or end of the file.
To decrypt the RSA private key, open a Command Prompt window and navigate to C:\software\OpenSSL-Win32\bin.
1. Execute the following command:
```
openssl rsa -in C:\encrypted.pem -out C:\key.pem
```
2. When OpenSSL prompts you for the pass phrase, enter the PEM password you created earlier.
To convert the PEM files to DER files, open a Command Prompt window and navigate to C:\software\OpenSSL-Win32\bin.
1. Execute the following two commands:
```
openssl pkcs8 -topk8 -nocrypt -in C:\key.pem -inform PEM -out C:\key.der -outform DER
openssl x509 -in C:\cert.pem -inform PEM -out C:\cert.der -outform DER
```
  Once these commands are completed, you have two DER files.
2. We recommend deleting the PFX and PEM files at this point.
To copy ImportKey.class to the Java JDK bin folder (C:\software\jdk-11.0.1\bin in our example), open a Command Prompt, navigate to C:\software\jdk-11.0.1\bin and execute the following command to merge the two DER certificate files into a single Java keystore.
```
java ImportKey C:\key.der C:\cert.der
```
1. Note the following line: Using keystore-file : C:\Users\USERNAME\keystore.ImportKey.
2. Navigate to the above directory, rename the keystore.ImportKey file to as400.jks and then copy it to the IdentityForge \conf directory (C:\ldapgateway\conf in our example).

To configure IdentityForge to point to this Java keystore, open C:\ldapgateway\dist\idfserver\beans.xml in the text editor of your choice and scroll to the following section to change the Java keystore filename testnew.jks:

<bean id="sslChannelFactory" class="com.identityforge.idfserver.nio.ssl.SSLChannelFactory">
<constructor-arg><value>false</value></constructor-arg>
<constructor-arg><value>../conf/testnew.jks</value></constructor-arg>
<constructor-arg><value>abc123</value></constructor-arg>
<constructor-arg><value>false</value></constructor-arg>
</bean>

Change the second constructor-arg value to the name of the Java keystore we created earlier. For example:

<bean id="sslChannelFactory" class="com.identityforge.idfserver.nio.ssl.SSLChannelFactory">
<constructor-arg><value>false</value></constructor-arg>
<constructor-arg><value>../conf/as400.jks</value></constructor-arg>
<constructor-arg><value>abc123</value></constructor-arg>
<constructor-arg><value>false</value></constructor-arg>
</bean>

To set the Java keystore password, change the Java keystore password abc123:

<bean id="sslChannelFactory" class="com.identityforge.idfserver.nio.ssl.SSLChannelFactory">
<constructor-arg><value>false</value></constructor-arg>
<constructor-arg><value>../conf/as400.jks</value></constructor-arg>
<constructor-arg><value>abc123</value></constructor-arg>
<constructor-arg><value>false</value></constructor-arg>
</bean>

Open C:\ldapgateway\dist\propertyEncrypt.bat in the text editor of your choice.
1. Scroll to the end of the propertyEncrypt.bat file until you see the following lines of code:
```
rem Start Property Encrypt Utility
%JAVACMD%  %JVM_OPTS%  -cp %CLASSPATH%  com.identityforge.idfserver.util.AESCipherUtil
idfRacfPwd
```
2. Change idfRacfPwd to the password of the Java keystore. The default password is importkey. If you changed the keystore password earlier, please enter that value here instead. When finished, save the propertyEncrypt.bat file.

Double-click propertyEncrypt.bat to see output similar to the following:

New encrypted string as HEX: 10902AA71C4DF819C965E8B5B7DF0208

Copy this value (in our example, 10902AA71C4DF819C965E8B5B7DF0208) to the clipboard. Change the Java keystore password in the third constructor-arg to the encrypted password string in the clipboard. For example:

<bean id="sslChannelFactory" class="com.identityforge.idfserver.nio.ssl.SSLChannelFactory">
<constructor-arg><value>false</value></constructor-arg>
<constructor-arg><value>../conf/as400.jks</value></constructor-arg>
<constructor-arg><value>10902AA71C4DF819C965E8B5B7DF0208</value></constructor-arg>
<constructor-arg><value>false</value></constructor-arg>
</bean>

Finally, since we are using an encrypted password for the Java keystore, we need to change the last constructor-arg value to true. For example:

<bean id="sslChannelFactory" class="com.identityforge.idfserver.nio.ssl.SSLChannelFactory">
<constructor-arg><value>false</value></constructor-arg>
<constructor-arg><value>../conf/as400.jks</value></constructor-arg>
<constructor-arg><value>10902AA71C4DF819C965E8B5B7DF0208</value></constructor-arg>
<constructor-arg><value>true</value></constructor-arg>
</bean>

To configure SSL for the AS/400

To configure secure communications between the IdentityForge server and the AS/400 we need to retrieve the SSL certificate from the OS/400 Certificate Manager.

From a web browser, navigate to the Digital Certificate Manager on http://OS400domain:2001, where OS400domain is the OS/400 target system. Use the same user account and password that you use to access the OS/400.
In the left panel, select Create Certificate Authority. If the Create Certificate Authority setting is not an option, select Install Local CA Certificate on Your PC.
Select Install Certificate and copy the certificate to a text file. In our example we are copying the cert to the root of the partition, to C:\cert.cer.
Open a Command Prompt and navigate to the Java JDK bin folder. In our example, this is C:\software\jdk-11.0.1\bin. Execute the following command:
```
keytool -importcert -file C:\cert.cer -alias arbitraryaliashere -keystore C:\software\jdk-11.0.1\jre\lib\security\cacerts
```
The alias is just a text string used to reference the certificate–you can enter any value. Enter the default JDK keystore password, "changeit," to confirm the addition.
To verify the presence of the certificate in the certificate store, run the following command:
```
keytool -list -keystore C:\software\jdk-11.0.1\jre\lib\security\cacerts
```
Enter the defaukt JDK keystore password, "changeit," to view the contents of the Java keystore.
To allow IdentityForge and AS/400 to communicate through a firewall, the following ports may need to be opened between the IdentityForge server and the AS/400:
- Port 446 (TCP) DDM
- Port 448 (TCP) Secure DDM
- Port 449 (TCP) Server mapper
- Port 8470 (TCP) Central server
- Port 8475 (TCP) Remote command and program call server
- Port 8476 (TCP) Signon server
- Port 9470 (TCP) Secure central server
- Port 9475 (TCP) Secure remote command/ Program call server
- Port 9476 (TCP) Secure signon server
For more information, please see the following JTOpen and IBM iSeries documentation pages:
- Toolbox for Java and JTOpen
- Port numbers for host servers and server mapper

To package the IdentityForge environment

Navigate to C:\ldapgateway\dist\idfserver, press CTRL+A to select all of files and folders in this location, then right click and choose Send to, then Compressed (zipped) folder. This creates a .zip file in the C:\ldapgateway\dist\idfserver directory.
Rename the .zip file to idfserver.jar. Copy idfserver.jar to C:\ldapgateway\dist.
Overwrite the existing file.

To configure the IdentityForge windows service wrapper

Execute C:\ldapgateway\bin\run.bat to start the IdentityForge server.
To host the IdentityForge java executable as a windows service, navigate to C:\ldapgateway\win_service and open IDF-Win-Server.bat in the text editor of your choice.
Scroll to the section shown below to change the JAVA_HOME and JVM path variables listed here:
```
set JAVA_HOME=C:\Program Files\Java\jre7
set JVM=C:\Program Files\Java\jre7\bin\client\jvm.dll
```
Change this path to point to the installation path of the Java JDK. In our example, we change it to the following:
```
set JAVA_HOME=C:\software\jdk-11.0.1
set JVM=C:\software\jdk-11.0.1\jre\bin\client\jvm.dll
```
Scroll through the IDF-Win-Service.bat file until you see the HOME and APPLICATION_SERVICE_HOME variables listed here:
```
set HOME=C:\ldfService\ldapgateway
set APPLICATION_SERVICE_HOME=C:\ldfService\ldapgateway\win_service
```
Change this path to point to the IdentityForge installation directory. In our example, we change it to the following:
```
set HOME=C:\ldapgateway
set APPLICATION_SERVICE_HOME=C:\ldapgateway\win_service
```
Scroll through the IDF-Win-Service.bat file until you see this SERVICE_NAME value:
```
set SERVICE_NAME=IdentityForgeService
```
Change this variable to a name to use for the Windows service as shown in Service Manager.
Scroll through the IDF-Win-Service.bat file until you see the CG_STDOUTPUT variable listed below:
```
set CG_STDOUTPUT=%CG_LOGPATH%\IDFServiceOut.log
```
In order to disable verbose logging, change this line to the following:
```
REM -- set CG_STDOUTPUT=%CG_LOGPATH%\IDFServiceOut.log
```
Scroll through the IDF-Win-Service.bat file until you see the CG_DESCRIPTION and CG_DISPLAY_NAME values listed here:
```
Set CG_DESCRIPTION="Identity Forge Service for LDAP Gateway"
set CG_DISPLAY_NAME=IdentityForgeService
```
Change these variables to text for the description and display name of the Windows service as shown in Service Manager.
Open a Command Prompt window and navigate to C:\ldapgateway\win_service.
Execute the following command:
```
IDF-Win-Service.bat install
```
If you wish to remove the service at a later date, execute the following command:
```
IDF-Win-Service.bat remove
```

In this article

Browser not supported