Secure Sockets Layer (SSL) provides secure connections by encrypting the data exchanged between a client and an AS/400 server session and by performing server authentication. There is an increased cost in performance with SSL because SSL connections perform slower than connections without encryption. SSL can be used only with an SSL capable AS/400 running OS/400, V4R4 or later. You use SSL connections when the sensitivity of the data transferred merits the increased cost in performance, for example, credit card or bank statement information.
AS/400 Toolbox for Java does not contain the algorithms needed to encrypt and decrypt data. These algorithms are shipped with AS/400 licensed programs 5769-CE1, 5769-CE2, and 5769-CE3. You need to order one of the 5769-CEx product versions of SSL depending on the country in which you live. Contact your IBM representative for more information or to order:
Before you begin using SSL with AS/400 Toolbox for Java:
Once you point to SSL in your CLASSPATH, the server certificate authenticates the connection with the AS/400. Without a certificate, SSL will not work. You can use two types of certificates: certificates from a trusted authority or certificates that you build.
If you are using certificates issued by a trusted authority, you need to do a few steps. Afterward, the certificate keyring is set up for you, the connection is secure, and SSL is working for you.
AS/400 Toolbox for Java supports certificates issued by the following trusted authorities:
If you choose not to use a certificate from a trusted authority, you can also build your own certificate. You should only build your own certificate if you are concerned with cost, need more control than a trusted authority certificate would give you, or are just using it to put together a local intranet.
[ Information Center Home Page | Feedback ] | [ Legal | AS/400 Glossary ] |