Technical Notes |
|
This technical note describes how to set up Reflection for IBM 2008 or 2007 to connect over SSL-enabled Telnet to an iSeries or AS/400, using a self-signed certificate.
The security for Reflection depends upon the security of the operating system, host, and network environment. We strongly recommend that you evaluate and implement all relevant security service packs, updates, and patches recommended by your operating system, host, and network manufacturers.
The recommendations in this note are general guidelines and should be evaluated in the context of your own computing needs and environment. These general steps can also be used to configure Reflection to utilize a registered digital signature and key pair (from a certifying authority); however, it is recommended that you configure and test your SSL environment using a self-signed certificate before implementing a production certificate from a certificate authority.
Setting up Reflection for IBM 2008 or 2007 to connect to an iSeries or AS/400 over SSL involves these steps:
Before creating SSL certificates, the Digital Certificate Manager (Option 34 of 57xx-SS1) utility and the Cryptographic Access Provider (57xx-AC3) must be installed and configured on your AS/400.
Verify that TCP is configured and running on the AS/400 before proceeding.
Using the Digital Certificate Manager (DCM), create a self-signed certificate and assign it to the Telnet Server. For more information on creating certificates and assigning certificates to applications, see the iSeries Information Center at http://publib.boulder.ibm.com/iseries/.
The self-signed server certificate can either be saved to a file (by selecting Copy and Paste Certificate) or, for testing purposes, it can be saved directly to your workstation (by selecting Install Certificate).
If you choose Copy and Paste Certificate, you will need to manually integrate the certificate with Internet Explorer. (See steps in Transfer or Extract the Certificate.)
If you choose Install Certificate, the certificate is installed to your workstation and is automatically added to Internet Explorer.
To apply the updates to the TCP/IP server, cycle the iSeries or AS/400 TCP/IP stack. Once you have done this, you will be able to see that the port you have configured for the secure connections is listening.
Execute the OS/400 command NETSTAT *CNN to verify that the port is up and listening for the telnet-ssl local port.
Sample display:
| Remote Address |
Remote Port |
Local Port |
Idle Time |
State |
| * |
* |
www |
001:30:33 |
Listen |
| * |
* |
telnet |
261:48:39 |
Listen |
| * |
* |
telnet -> |
070:54:37 |
Listen |
Note: The Local Port entry telnet-> expands to telnet-ssl. Press F14 to view the port number where telnet SSL is running.
When creating the self-signed certificate using the DCM, if you chose Copy and Paste Certificate, rather than Install Certificate, follow these steps to manually integrate the certificate with Internet Explorer.
The new certificate is displayed in the Trusted Root Certification Authorities list.
To make an SSL connection using Reflection for IBM 2008 or 2007:
By default, Reflection opens by displaying the Create New Document dialog box. (Alternate navigation to Create New Document: click the upper-left icon and click New.)
To verify the port number, use the OS/400 NETSTAT *CNN command, and view the port entry for telnet-ssl. (The Telnet-SSL heading may be displayed as telnet->.)
This link is a shortcut to the Security section of the Configure Advanced Connection (or 5250) Settings dialog box.
For testing purposes, accept the Encryption strength Default setting.
Once you have successfully connected, a blue and gray padlock icon displays in the Reflection display status bar, indicating that your connection is secure.
If you are unable to connect using SSL, try again with the following configurations.