Configuring Identity Forge for EmpowerID

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


To install and configure the Java environment

  1. Execute the Java JDK installer and click Next.
  2. On the optional features page, change Public JRE to This feature will not be available and change Source Code to This feature will not be available.
  3. Click Development Tools and then click the Change button.
  4. Change C:\Program Files (x86)\Java\jdk1.7.0_25 to a shorter path without spaces in it, such as C:\software\jdk1.7.0_25\.
  5. Click Next to begin the installation.
  6. Click Close when finished.
  7. Open Control Panel by clicking Start, typing Control and pressing ENTER.
  8. From Control Panel, navigate to System > Advanced system settings and then click Environment Variables.
  9. In the System variables pane of the Environment Variables window that appears, click New.
  10. In the New System Variable dialog that appears, do the following:
    1. Type JAVA_HOME in the Variable name field
    2. Type the installation path of the Java JDK, such as C:\software\jdk1.7._25, in the Variable value field
    3. Click OK to close the dialog.
  11. Close the Environment Variables and System Properties windows and then close Control Panel.
  12. Extract i5_advanced_adapter_5.0.0.4_enterprise.zip to the root of the partition (C:\ in our example) and then navigate to C:\i5_Advanced_Adapter_5.0.0.4_Enterprise\etc\LDAP Gateway.
  13. Extract ldapgateway.zip to the root of the partition (C:\ in our example).
  14. Extract jtopen_7_10.zip to a folder named jtopen_7_10 in the root of the partition (C:\ in our example).
  15. Navigate to C:\jtopen_7_10\lib\ and copy jt400.jar and util400.jar to C:\ldapgateway\lib.
  16. Navigate to C:\ldapgateway\bin and open run.bat in the text editor of your choice.
  17. Adjust the following line to the installation path of the Java JDK:
    set JAVA_HOME=\software\jdk1.6.0_16

    In our example, this line would be changed to the following:

    set JAVA_HOME=C:\software\jdk1.7.0_25

To configure the IdentityForge as400.properties file

  1. Navigate to C:\ldapgateway\conf and open as400.properties in the text editor of your choice.
  2. From the text editor, change the following parameter to true:
    _isSSL_
  3. Adjust the following parameters with the IP address of your target iSeries:
    _host_ 
        _agentHost_
  4. Adjust the following parameters with the UID of the administrative AS/400 account:
    _adminId_            
        _agentAdminId_
  5. Place a '#' in front of the following parameters to comment them out:
    _adminPwd_           
        _agentAdminPwd_
  6. Remove the '#' from the following parameters to uncomment them:
    _adminPwdEncrypt_            
        _agentAdminPwdEncrypt_

  7. Clear text is not desirable for the passwords in the as400.properties file, so we will need to encrypt them using propertyEncrypt.bat.

  8. Copy C:\i5_Advanced_Adapter_5.0.0.4_Enterprise\scripts\propertyEncrypt.bat to C:\ldapgateway\dist and then open C:\ldapgateway\dist\propertyEncrypt.bat in the text editor of your choice.
  9. 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 would be changed to the following:

    set JAVA_HOME=C:\software\jdk1.7.0_25
  10. Scroll through the propertyEncrypt.bat file until you see the following line:
    SET CLASSPATH=C:\software\identityforge\ldapgateway\dist\idfserver.jar

    This path needs to point to the IdentityForge installation directory. In our example, this line would be changed to the following:

    SET CLASSPATH=C:\ldapgateway\dist\idfserver.jar
  11. 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
  12. Change the bolded text to the password of the AS/400 administrative account, then save the propertyEncrypt.bat file.
  13. Double-click propertyEncrypt.bat. You should see something similar to the following output:
    New encrypted string as HEX: 10902AA71C4DF819C965E8B5B7DF0208
  14. Copy this value (in our example, 10902AA71C4DF819C965E8B5B7DF0208) to the clipboard.
  15. Navigate to C:\ldapgateway\conf and open as400.properties in the text editor of your choice.
  16. Paste the value into the following parameters:
    _adminPwdEncrypt_
        _agentAdminPwdEncrypt_
  17. Here is an example of a completed as400.properties file:

    # USE SSL
        _isSSL_=true
        # HOST/IP VALUE TO CALL i5
        _host_=74.125.225.114
        # ADMIN ID TO CONNECT TO i5
        _adminId_=AS400ADMIN
        # ADMIN PASSWORD
        #_adminPwd_=
        # ADMIN ENCRYPTED PASSWORD
        _adminPwdEncrypt_=10902AA71C4DF819C965E8B5B7DF0208
        # HOST/IP WHERE AGENT RUNNING
        _agentHost_=74.125.225.114
        # ADMIN ID
        _agentAdminId_=AS400ADMIN 
        # ADMIN PASSWORD
        #_agentAdminPwd_=
        # ADMIN ENCRYPTED PASSWORD
        _agentAdminPwdEncrypt_=10902AA71C4DF819C965E8B5B7DF0208

To unpack the IdentityForge environment

  1. Navigate to C:\ldapgateway\dist and rename idfserver.jar to idfserver.zip.
  2. 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.

  1. Open C:\ldapgateway\dist\idfserver\beans.xml in the text editor of you choice and scroll to the below section. We will be changing the value for theFront-End LDAP administrative account listed in bold:
    <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 provides the ability to have two Front-End LDAP administrative accounts, but for our purposes we only need one.

  2. 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"/>

  3. Now we need to change the password for the Front-End LDAP administrative account.

    Clear text is not desirable for the password in the beans.xml file, so we will need to encrypt it using propertyEncrypt.bat.

  4. Open C:\ldapgateway\dist\propertyEncrypt.bat in the text editor of yur choice.
  5. 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
  6. Change the bolded text to the password of the Front-End LDAP administrative account and then save the propertyEncrypt.bat file.
  7. Double-click propertyEncrypt.bat. You should see something similar to the following output:
    New encrypted string as HEX: 10902AA71C4DF819C965E8B5B7DF0208
  8. Copy the value (in our example, 10902AA71C4DF819C965E8B5B7DF0208) to the clipboard.
  9. 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.

  1. Open C:\ldapgateway\dist\idfserver\beans.xml in the text editor of your choice.
  2. Scroll to the section shown below. We will be changing the Back-End LDAP administrative account password listed in bold:
    <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"/>
  3. Clear text is not desirable for the password in the beans.xml file, so we will need to encrypt it using propertyEncrypt.bat.

  4. Open C:\ldapgateway\dist\propertyEncrypt.bat in the text editor of your choice.
  5. 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
  6. Change the bolded text to the password of the Back-End LDAP administrative account and then save the propertyEncrypt.bat file.
  7. Double-click propertyEncrypt.bat. You should see something similar to the following output:
    New encrypted string as HEX: 10902AA71C4DF819C965E8B5B7DF0208
  8. Copy the value (in our example, 10902AA71C4DF819C965E8B5B7DF0208) to the clipboard.
  9. 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

  1. To configure secure communications between EmpowerID and the IdentityForge LDAP server we will 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.
    If your EmpowerID certificate is not already available in PFX format, use the Certificates MMC snap-in to export the certificate and the corresponding private key to a PFX file. Be sure to note the pass phrase used to protect the PFX file; it will be needed later. If the certificate and its corresponding private key is already available in PFX format and the pass phrase for the PFX file is known, we can skip this step.

  2. Install the Microsoft Visual C++ 2008 Redistributable Package (x86) by running vcredist_x86.exe.
  3. Next, install Win32 OpenSSL v1.0.1e Light by running Win32OpenSSL_Light-1_0_1e.exe. In our example, we are choosing an installation path of C:\software\OpenSSL-Win32.
  4. Click Next. When prompted where to copy the OpenSSL DLLs, choose The OpenSSL binaries (/bin) directory.
  5. Click Next and finish the installation.
  6. Copy the PFX certificate (named EIDcert.pfx in our example) to the root of the partition (C:\ in our example).
  7. Open a Command Prompt window and navigate to C:\software\OpenSSL-Win32\bin.
  8. 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 will ask 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 will be the password you set on the certificate during the export.

  9. Enter the password for the certificate and press ENTER.
  10. Next OpenSSL will prompt for the PEM pass phrase. We are setting a new pass phrase here—make sure to remember this value! You can use the same password as the import password if you want. Enter the pass phrase and press ENTER, then enter the pass phrase again to confirm and press ENTER once more. We now have a PEM file available at C:\EIDcert.pem.
  11. Using a text editor of your choice, open the PEM file (C:\EIDcert.pem in our example). We need to extract the private key and place it in a separate file.
  12. Find the following lines below:
    
        -----BEGIN ENCRYPTED PRIVATE KEY-----
                    DATA HERE
        -----END ENCRYPTED PRIVATE KEY-----
            
  13. 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.
  14. Next, we need to pull out the public key and put it into a separate file. Find the following lines below:
    
        -----BEGIN CERTIFICATE-----
                DATA HERE
        -----END CERTIFICATE-----
            
  15. 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.
  16. Next, we need to decrypt the RSA private key.
  17. Open a Command Prompt window and navigate to C:\software\OpenSSL-Win32\bin.
  18. Execute the following command:
    openssl rsa -in C:\encrypted.pem -out C:\key.pem
  19. When OpenSSL prompts you for the pass phrase, enter the PEM password you created earlier.

  20. Be sure to guard the unencrypted private key (C:\key.pem in our example) with extreme caution as loss of this file can result in compromise of your system. EmpowerID recommends deleting this file after the next conversion.

  21. Next, we need to convert the PEM files to DER files.
  22. Open a Command Prompt window and navigate to C:\software\OpenSSL-Win32\bin.
  23. 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 will have two DER files. At this time it is recommended to delete the PFX and PEM files.

  24. Next, copy ImportKey.class to the Java JDK bin folder (C:\software\jdk1.7.0_25\bin in our example).
  25. Open a Command Prompt, navigate to C:\software\jdk1.7.0_25\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

    Note the following line: “Using keystore-file : C:\Users\USERNAME\keystore.ImportKey”.
  26. 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).

  27. The default password on the Java keystore is “importkey” without the quotes. If you want to change the Java keystore password, open a Command Prompt and navigate to C:\software\jdk1.7.0_25\bin, then execute the following command:
    keytool -storepasswd -new NEWPASSWORDHERE -keystore C:\ldapgateway\conf\as400.jks

    You will be prompted for the old Java keystore password, and then the new password will be set. Remember this password as it will be used later.


  28. Finally, we need 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. We will be changing the Java keystore filename listed in bold:
    <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>
  29. 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>
  30. The final step is to set the Java keystore password. We will be changing the Java keystore password listed in bold:
    <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>
  31. Clear text is not desirable for the password in the beans.xml file, so we will need to encrypt it using propertyEncrypt.bat.
  32. Open C:\ldapgateway\dist\propertyEncrypt.bat in the text editor of your choice.
  33. 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
  34. Change the bolded text to the password of the Java keystore. The default password is “importkey” without the quotes – if you changed the keystore password earlier, please enter that value here instead. When finished, save the propertyEncrypt.bat file.
  35. Double-click propertyEncrypt.bat. You should see something similar to the following output:
    New encrypted string as HEX: 10902AA71C4DF819C965E8B5B7DF0208
  36. Copy this value (in our example, 10902AA71C4DF819C965E8B5B7DF0208) to the clipboard. Change the Java keystore password listed in bold 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>
  37. 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 will need to retrieve the SSL certificate from the OS/400 Certificate Manager.

  1. 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.
  2. 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.
  3. 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.
  4. We now need to add the SSL certificate from the OS/400 system to the Java JDK keystore.

  5. Open a Command Prompt and navigate to the Java JDK bin folder. In our example, this is C:\software\jdk1.7.0_25\bin. Execute the following command:
    
        keytool -importcert -file C:\cert.cer -alias arbitraryaliashere -keystore C:\software\jdk1.7.0_25\jre\lib\security\cacerts
  6. 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.
  7. To verify the presence of the certificate in the certificate store, run the following command:
    keytool -list -keystore C:\software\jdk1.7.0_25\jre\lib\security\cacerts
  8. 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 serve
  • 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:

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 > Compressed (zipped) folder. This will create 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

  1. Execute C:\ldapgateway\bin\run.bat to start the IdentityForge server.
  2. 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.
  3. Scroll to the section shown below. We will be changing the JAVA_HOME and JVM path variables listed in bold:
    set JAVA_HOME=C:\Program Files\Java\jre7
        set JVM=C:\Program Files\Java\jre7\bin\client\jvm.dll

    This path needs to point to the installation path of the Java JDK. In our example, this line would be changed to the following:

    set JAVA_HOME=C:\software\jdk1.7.0_25
        set JVM=C:\software\jdk1.7.0_25\jre\bin\client\jvm.dll
  4. Scroll through the IDF-Win-Service.bat file until you see the HOME and APPLICATION_SERVICE_HOME variables listed in bold:
    set HOME=C:\ldfService\ldapgateway
        set APPLICATION_SERVICE_HOME=C:\ldfService\ldapgateway\win_service

    This path needs to point to the IdentityForge installation directory. In our example, this line would be changed to the following:

    set HOME=C:\ldapgateway
        set APPLICATION_SERVICE_HOME=C:\ldapgateway\win_service
  5. Scroll through the IDF-Win-Service.bat file until you see the SERVICE_NAME value listed in bold:
    set SERVICE_NAME=IdentityForgeService

    This variable can be changed to a name of your choosing. This will be the name of the Windows service as shown in Service Manager.

  6. 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, this line should be changed to the following:

    REM -- set CG_STDOUTPUT=%CG_LOGPATH%\IDFServiceOut.log
  7. Scroll through the IDF-Win-Service.bat file until you see the CG_DESCRIPTION and CG_DISPLAY_NAME values listed in bold:
    Set CG_DESCRIPTION=”Identity Forge Service for LDAP Gateway”
        set CG_DISPLAY_NAME=IdentityForgeService

    These variables can be changed as you see fit. The text will become the description and the display name of the Windows service as shown in Service Manager, respectively.

  8. Open a Command Prompt window and navigate to C:\ldapgateway\win_service.
  9. Execute the following command:
    IDF-Win-Service.bat install
  10. If you wish to remove the service at a later date, execute the following command:
    IDF-Win-Service.bat remove
  • Troubleshooting and monitoring the IdentityForge server
    To check and monitor the IdentityForge log files, look for the log files located in C:\ldapgateway\logs.

    To enable Java debugging do the following:

    1. Open C:\ldapgateway\bin\run.bat in the text editor of your choice and scroll down to the following lines:
      rem Start Ldap Gateway Server
          %JAVACMD% %DEBUG% %JVM_OPTS% %SECURE% -cp %CLASSPATH% com.identityforge.idfserver.Main %1 %2 %3 %4 %5 %6 %7 %8 %9
    2. Add -javax.net.debug=all directly after the %CLASSPATH% variable. Once completed, it should look like the following:
      rem Start Ldap Gateway Server
          %JAVACMD% %DEBUG% %JVM_OPTS% %SECURE% -cp %CLASSPATH% -Djavax.net.debug=all com.identityforge.idfserver.Main %1 %2 %3 %4 %5 %6 %7 %8 %9
    3. Execute C:\ldapgateway\bin\run.bat to start the IdentityForge server with Java debugging enabled.

    To increase the memory available to the Java JVM, do the following:

    1. Open C:\ldapgateway\bin\run.bat in the text editor of your choice and scroll down to the following lines:
      rem Start Ldap Gateway Server
          %JAVACMD% %DEBUG% %JVM_OPTS% %SECURE% -cp %CLASSPATH% com.identityforge.idfserver.Main %1 %2 %3 %4 %5 %6 %7 %8 %9
    2. Add -Xms512>m -Xmx1024m directly after the %CLASSPATH% variable. Once completed, it should look like the following:
      rem Start Ldap Gateway Server
          %JAVACMD% %DEBUG% %JVM_OPTS% %SECURE% -cp %CLASSPATH% -Xms512m -Xmx1024m com.identityforge.idfserver.Main %1 %2 %3 %4 %5 %6 %7 %8 %9
    3. Execute C:\ldapgateway\bin\run.bat to start the IdentityForge server with the specified minimum and maximum memory available to the Java JVM.