ibm-information-center/dist/eclipse/plugins/i5OS.ic.rzakx_5.4.0.1/rzakxsslregistryentry.htm

63 lines
5.6 KiB
HTML
Raw Normal View History

2024-04-02 14:02:31 +00:00
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE html
PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html lang="en-us" xml:lang="en-us">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
<meta name="copyright" content="(C) Copyright IBM Corporation 2005" />
<meta name="DC.rights.owner" content="(C) Copyright IBM Corporation 2005" />
<meta name="security" content="public" />
<meta name="Robots" content="index,follow" />
<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' />
<meta name="DC.Type" content="concept" />
<meta name="DC.Title" content="Secure Sockets Layer (SSL) registry entry" />
<meta name="abstract" content="iSeries Navigator users can request a secure connection to an iSeries server by selecting the Use Secure Sockets Layer checkbox on the Connection tab of the property sheet for iSeries objects. When this is done, only iSeries Navigator components that are capable of supporting SSL communications are enabled for activation by the user." />
<meta name="description" content="iSeries Navigator users can request a secure connection to an iSeries server by selecting the Use Secure Sockets Layer checkbox on the Connection tab of the property sheet for iSeries objects. When this is done, only iSeries Navigator components that are capable of supporting SSL communications are enabled for activation by the user." />
<meta name="DC.Relation" scheme="URI" content="rzakxcreateplugin.htm" />
<meta name="DC.Format" content="XHTML" />
<meta name="DC.Identifier" content="rzakxsslregistryentry" />
<meta name="DC.Language" content="en-us" />
<!-- All rights reserved. Licensed Materials Property of IBM -->
<!-- US Government Users Restricted Rights -->
<!-- Use, duplication or disclosure restricted by -->
<!-- GSA ADP Schedule Contract with IBM Corp. -->
<link rel="stylesheet" type="text/css" href="./ibmdita.css" />
<link rel="stylesheet" type="text/css" href="./ic.css" />
<title>Secure Sockets Layer (SSL) registry entry</title>
</head>
<body id="rzakxsslregistryentry"><a name="rzakxsslregistryentry"><!-- --></a>
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
<h1 class="topictitle1">Secure Sockets Layer (SSL) registry entry</h1>
<div><p>iSeries™ Navigator users can request a secure connection to an iSeries server by selecting the <span class="uicontrol">Use Secure Sockets Layer</span> checkbox on the <span class="uicontrol">Connection</span> tab of the property sheet for iSeries objects. When this is done, only iSeries Navigator components
that are capable of supporting SSL communications are enabled for activation by the user.</p>
<p>If all of a plug-in's communications with the iSeries server are managed by using the iSeries Access for Windows<sup>®</sup> system handle (enter cwbCO_SysHandle), or by using the
class <span class="uicontrol">com.ibm.as400.access.AS400</span> in the case of a Java™ plug-in, then it should indicate that
it supports secure connections to the iSeries server. For C++ plug-ins, the cwbCO_SysHandle is obtained by calling the cwbUN_GetSystemHandle
API. When the user requests a secure connection, the Navigator automatically will enable SSL. In the case of Java plug-ins,
the iSeries server object obtained by calling the <span class="uicontrol">getSystemObject</span> method on the class <span class="uicontrol">com.ibm.as400.opnav.ObjectName</span> actually
will be an instance of <span class="uicontrol">com.ibm.as400.access.SecureAS400</span>.</p>
<div class="note"><span class="notetitle">Note:</span> If you are running Java over SSL, and creating your own CA certificate, iSeries Access for Windows GA service pack is required.</div>
<p>If a plug-in's communications with the iSeries server are performed by using the Sockets API or some other low-level communications
service, then it is the responsibility of the plug-in to support SSL if it has been requested. If the plug-in doesn't provide this support, it should indicate that it doesn't support SSL as described below.
When this is done, the plug-in's function will be disabled if the user has requested a secure connection.</p>
<dl><dt class="dlterm">Example: Adding a registry key to enable SSL</dt>
<dd>The key is SSL under <samp class="codeph">[HKEY_CLASSES_ROOT\IBM.AS400.Network\3RD PARTY EXTENSIONS\IBM.Sample\SSL] "Support Level"=dword:00000001</samp> where <samp class="codeph">IBM.Sample</samp> is the plug-in supplied
product component.<div class="note"><span class="notetitle">Note:</span> <samp class="codeph">"Support Level"=dword:00000001</samp> = supports SSL, and <samp class="codeph">"Support Level"=dword:00000000</samp> = does NOT support SSL.</div>
</dd>
<dt class="dlterm"></dt>
<dd> <pre> ;------------------------------------------------------------------------------
; Example registry key that
says this plug-in supports SSL
{HKEY_CLASSES_ROOT\IBM.AS400.Network\3RD PARTY EXTENSIONS\IBM.Sample\SSL}
"Support Level"=dword:00000001</pre>
</dd>
</dl>
</div>
<div>
<div class="familylinks">
<div class="parentlink"><strong>Parent topic:</strong> <a href="rzakxcreateplugin.htm" title="After modifying the sample plug-ins, you'll need to make some modifications to the registry files. This topic provides a walk-through of the registry files for each type of plug-in, and recommends some modifications.">Customize the plug-in registry files</a></div>
</div>
</div>
</body>
</html>