The OS/400 Connector is installed with CA IAM Connector Server.
To migrate from the C++ OS/400 connector to the Java OS/400 connector, you must do the following:
Once this has been done, all types of operations can be executed against the existing OS400 endpoints seamlessly.
You must configure your OS/400 system to use the OS/400 connector. To do this, install and configure programs on your OS/400 system.
Install and Configure Programs on OS/400
The JTOPEN toolkit used by the OS/400 connector requires the following programs to be installed and configured on your OS/400 system:
These programs are necessary so the OS/400 connector can connect to your OS/400 system and access its data and services.
You can send information through secured or unsecured channels.
For security purposes, we recommend that you secure the communications between all your machines. To do this, you must configure the following:
Connect Using SSL
Communication between the Provisioning Server/CA IAM Connector Server and the OS/400 machine is secured by SSL. Using SSL is optional in both links and can be switched on when acquiring the OS/400 machine. Certificates are used to authenticate the server and encrypt communications and the username and password are used to authenticate the client request on the OS/400 machine.
To use SSL, the CA IAM Connector Server machine must have the endpoint certificate installed in the Java certificate store in the JRE in which CA IAM Connector Server machine is running.
Configure Your OS/400 System
Secure the channel between CA IAM Connector Server and your OS/400 system by performing these steps:
Prepare the System
To prepare your OS/400 system, perform the following procedure:
On your OS/400 system
IBM iSeries Client Encryption (56-bit) Version 5, Release 1. This program is used in countries other than the United States or Canada.
IBM iSeries Client Encryption (128-bit) Version 5, Release 1. This program is used in the United States and Canada only.
IBM iSeries Client Encryption (56-bit) Version 4, Release 5. This program is used in countries other than the United States or Canada.
IBM iSeries Client Encryption (128-bit) Version 4, Release 5. This program is used in the United States and Canada only.
Note: These programs are an installation option on your OS/400 system.
IBM iSeries Server Encryption (56-bit) Version 5, Release 1. This program is used in countries other than the United States or Canada.
IBM iSeries Server Encryption (56-bit) Version 4, Release 5. This program is used in countries other than the United States or Canada.
IBM iSeries Server Encryption (128-bit) Version 4, Release 5. This program is used in the United States and Canada only.
Note: These programs are an installation option on your OS/400 system.
Product Option 34 - Digital Certificate Manager
IBM HTTP Server
Select the Certificate Location
Select the location where you will import the certificate on your OS/400 system.
To select the location
STRTCPSVR SERVER(*HTTP) HTTPSVR(*ADMIN)
http://server:2001
Specifies the name of the system running OS/400.
Note: Your logon ID must have the All Object Access and System Configuration permissions.
The Digital Certificate Manager window appears. The left frame contains navigational buttons and the right frame contains command buttons.
Note: The steps that reference the Digital Certificate Manager are based on Version 5, Release 1. If you are using another version, these steps may vary slightly.
Import the Certificate Authority
Once you have selected the certificate location, import the certificate from your Certificate Authority (CA).
From the left frame
The Import Certificate window appears.
For example, enter: \home\etadmin\certificate_file_name.
The Digital Certificate Manager reads the certificate file and imports it into the system.
Request a Server Certificate from the CA
After importing the Certificate Authority, you must now request a server certificate.
From the CA
The Create Certificate window appears.
1024 bits
The name of your certificate
The name of your server
The name of your organization
The name of your state or province
The name of your country
Request a Server Certificate for Your System
To request a server certificate for your OS/400 system, follow this procedure:
From a Certificate Authority (CA)
where computer-name is the name of the computer for which you are generating the certificate. The Microsoft Certificate Services Wizard appears.
Note: Remember the location where you save the certificate.
Import the Server Certificate
Once you generate a server certificate, you can import it into the system.
From the CA
The Import Certificate window appears.
For example, enter: \home\etadmin\usildaaj.cer.
Assign the Server Certificate to Your OS/400 Applications
After importing the certificate, you must assign the server certificate to the following applications:
From the CA
The Update Certificate Assignment window appears.
ENDHOSTSVR *CENTRAL ENDHOSTSVR *RMTCMD
ENDHOSTSVR *SIGNON
STRHOSTSVR *CENTRAL RQDPCL(*TCP) STRHOSTSVR *RMTCMD RQDPCL(*TCP) STRHOSTSVR *SIGNON RQDPCL(*TCP)
Configure CA IAM Connector Server
If you are using a certificate from one of the following CAs, you do not need to perform this step:
If you want to use a certificate from a different CA, import the certificate into CA IAM Connector Server. If you use the same certificate for each OS/400 system, you will perform these steps only once.
Follow these steps: NEW STEPS
This tab lists all of the certificates in the CA IAM Connector Server keystore. To filter the list of certificates by their names, type in the Certificate Filter box.
Add a certificate:
Add a keystore:
Follow these steps: OLD STEPS
cd C:\Program Files\CA\Identity Manager\Connector Server\conf\
..\..\bin\keytool -import -alias "eTrust Admin CA Certificate" -file certificate_name.cer -keystore ssl.keystore
Note: You can use bin\ ldaps_password.bat utility to change the keystore's password.
The Password Synchronization agent lets password changes, made on the OS/400 endpoint system, be propagated to your other accounts managed by CA Identity Manager. For more information, see the CA Identity Manager Administrator's Guide.
For this release of CA Identity Manager, the OS/400 Connector does not support FIPs or IPv6.
The OS/400 Password Synchronization Agent also does not support FIPS or IPv6.
|
Copyright © 2014 CA.
All rights reserved.
|
|