ibm-information-center/dist/eclipse/plugins/i5OS.ic.rzaiy_5.4.0.1/rzaiysysauth.htm

86 lines
6.3 KiB
HTML

<?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="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="reference" />
<meta name="DC.Title" content="System authentication" />
<meta name="abstract" content="PPP connections with an iSeries server support several options for authenticating both remote clients dialing in to the iSeries, and connections to an ISP or other server that the iSeries is dialing." />
<meta name="description" content="PPP connections with an iSeries server support several options for authenticating both remote clients dialing in to the iSeries, and connections to an ISP or other server that the iSeries is dialing." />
<meta name="DC.Relation" scheme="URI" content="rzaiyplan.htm" />
<meta name="DC.Relation" scheme="URI" content="rzaiychap.htm" />
<meta name="DC.Relation" scheme="URI" content="rzaiyeap.htm" />
<meta name="DC.Relation" scheme="URI" content="rzaiypap.htm" />
<meta name="DC.Relation" scheme="URI" content="rzaiyradiusovw.htm" />
<meta name="DC.Relation" scheme="URI" content="rzaiyvalidlist.htm" />
<meta name="DC.Relation" scheme="URI" content="rzaiypppoe.htm" />
<meta name="DC.Relation" scheme="URI" content="rzaiyradiusexample.htm" />
<meta name="DC.Relation" scheme="URI" content="rzaiygrppol.htm" />
<meta name="copyright" content="(C) Copyright IBM Corporation 1998, 2006" />
<meta name="DC.Rights.Owner" content="(C) Copyright IBM Corporation 1998, 2006" />
<meta name="DC.Format" content="XHTML" />
<meta name="DC.Identifier" content="rzaiysysauth" />
<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>System authentication</title>
</head>
<body id="rzaiysysauth"><a name="rzaiysysauth"><!-- --></a>
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
<h1 class="topictitle1">System authentication</h1>
<div><p>PPP connections with an iSeries™ server support several options
for authenticating both remote clients dialing in to the iSeries, and
connections to an ISP or other server that the iSeries is dialing.</p>
<div class="section"><p>The iSeries supports
several methods for maintaining authentication information, ranging from simple
validation lists on the iSeries that contain lists of authorized users and
associated passwords, to support for RADIUS servers that maintain detailed
authentication information for your network users. The iSeries also supports several options
for encrypting user ID and password information, ranging from a simple password
exchange to maceration support with CHAP-MD5. You can specify your preferences
for system authentication, including a user ID and password used to validate
the iSeries when
dialing out, on the <strong>Authentication</strong> tab of the connection profile in iSeries Navigator. </p>
</div>
</div>
<div>
<ul class="ullinks">
<li class="ulchildlink"><strong><a href="rzaiychap.htm">CHAP-MD5</a></strong><br />
<strong>Challenge Handshake Authentication Protocol (CHAP-MD5)</strong> uses
an algorithm (MD-5) to calculate a value that is known only to the authenticating
system and the remote device.</li>
<li class="ulchildlink"><strong><a href="rzaiyeap.htm">EAP</a></strong><br />
<dfn class="term">Extensible Authentication Protocol (EAP)</dfn> allows third-party
authentication modules to interact with the PPP implementation.</li>
<li class="ulchildlink"><strong><a href="rzaiypap.htm">PAP</a></strong><br />
<dfn class="term">Password Authentication Protocol (PAP)</dfn> uses
a two-way handshake to provide the peer system with a simple method to establish
its identity.</li>
<li class="ulchildlink"><strong><a href="rzaiyradiusovw.htm">RADIUS overview</a></strong><br />
<dfn class="term">Remote Authentication Dial In User Service (RADIUS)</dfn> is
an Internet standard protocol which provides centralized authentication, accounting
and IP management services for remote access users in a distributed dial-up
network.</li>
<li class="ulchildlink"><strong><a href="rzaiyvalidlist.htm">Validation list</a></strong><br />
A validation list is used to store user ID and password information about remote users.</li>
</ul>
<div class="familylinks">
<div class="parentlink"><strong>Parent topic:</strong> <a href="rzaiyplan.htm" title="You can read this topic for information about creating and administering PPP connections.">Plan PPP</a></div>
</div>
<div class="relref"><strong>Related reference</strong><br />
<div><a href="rzaiypppoe.htm" title="Many ISPs offer high-speed Internet access over DSL using Point-to-Point Protocol over Ethernet (PPPoE). The iSeries server can connect to these service providers to offer high bandwidth connections that preserve the benefits of PPP.">Scenario: Connect your iSeries server to a PPPoE access concentrator</a></div>
<div><a href="rzaiyradiusexample.htm" title="A Network Access Server (NAS) running on the iSeries server can route authentication requests from dial-in clients to a separate RADIUS server. If authenticated, RADIUS can also control the IP addresses to the user.">Scenario: Authenticate dial-up connections with RADIUS NAS</a></div>
<div><a href="rzaiygrppol.htm" title="Group access policies identify distinct user groups for a connection, and allow you to apply common connection attributes and security settings to the entire group. In combination with IP filtering, this allows you to permit and restrict access to specific IP addresses on your network.">Scenario: Manage remote user access to resources using Group Policies and IP filtering</a></div>
</div>
</div>
</body>
</html>