Connecting to an iSeries or AS/400 Using SSL and Reflection for IBM

  • 7021684
  • 05-Jun-2003
  • 01-Apr-2018

Environment

Reflection for IBM version 11.0 through 14.x

Situation

This technical note describes how to set up Reflection for IBM to connect over SSL-enabled Telnet to an iSeries or AS/400, using a self-signed certificate.

Note: 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.

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 use 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.

Resolution

Setting up Reflection for IBM to connect to an iSeries or AS/400 over SSL involves these steps:
  1. Configure the AS/400 for SSL
  2. Create a Self-Signed Certificate
  3. Make a Connection

Note the following:

  • Once you have fully tested the SSL/TLS support, you can repeat step 2 using a Certificate Authority (CA) signed certificate.
  • Reflection's SSL/TLS support requires that Microsoft Internet Explorer be installed on the client machine. It need not be the primary browser, but Internet Explorer must be installed and configured to be able to manage and use the certificate.

Configure the AS/400 for SSL

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.

Please verify that TCP is configured and running on the AS/400 before proceeding.

Create a Self-Signed Certificate

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

Note the following:

  • While creating the certificate, enter the fully-qualified host name in the Common Name field of the certificate.
  • If you plan to implement client authentication, you must also create a client certificate. (Those steps are not provided in this technical note.)
  • The administrator must maintain physical security of the management server and proxy server. That is, no one other than the administrator should be able to physically access the servers, and no unauthorized individuals should be able to access the key store folders on the server. The security of the servers is important to prevent compromise of the certificates.

Saving the Self-Signed Certificate

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.

Verify the Setup

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.

Transfer or Extract the Certificate

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.

  1. From the Windows Control Panel, double-click Internet Options.
  2. On the Content tab, click Certificates.
  3. On the Trusted Root Certification Authorities tab, click Import > Next.
  4. Click Browse. Browse for and select your self-signed certificate file, and then click Open.
  5. Click Next, and then click Finish.
  6. When asked, "Do you want to ADD the following certificate to the Root Store," click Yes.

The new certificate is displayed in the Trusted Root Certification Authorities list.

Make a Connection

To make an SSL connection using Reflection:

  1. Start Reflection for IBM.
  2. Click Connection > Session Setup.
  3. In the Type drop-down list, select IBM 5250 Terminal.
  4. In the Host name or IP address field, enter the name of your mainframe as it appears in the Common Name field of the self-signed certificate. Typically, this is the fully qualified host name.
  5. In the Port field, enter the AS/400’s secure port number.

By default, this is Port 992. 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->.)

  1. Click Security.
  2. On the SSL/TLS tab, select Use SSL/TLS security.

For testing purposes, leave the Encryption strength at Default, and the "Certificate host name must match host being contacted" selected.

  1. Click OK, and then click Connect.

Once you have successfully connected, a blue and gray padlock icon is displayed in the OIA line indicating that your connection is secure.

Additional Information

Legacy KB ID

This document was originally published as Attachmate Technical Note 1747.

Feedback service temporarily unavailable. For content questions or problems, please contact Support.