64 lines
5.5 KiB
HTML
64 lines
5.5 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="concept" />
|
|
<meta name="DC.Title" content="Scenarios" />
|
|
<meta name="abstract" content="Use this information to review scenarios that illustrate typical single signon implementation situations to help you plan your own certificate implementation as part of your server security policy." />
|
|
<meta name="description" content="Use this information to review scenarios that illustrate typical single signon implementation situations to help you plan your own certificate implementation as part of your server security policy." />
|
|
<meta name="DC.Relation" scheme="URI" content="rzamzsso.htm" />
|
|
<meta name="DC.Relation" scheme="URI" content="rzamzenablesso.htm" />
|
|
<meta name="DC.Relation" scheme="URI" content="rzamzenablessoos400.htm" />
|
|
<meta name="DC.Relation" scheme="URI" content="rzamzsynchconfig.htm" />
|
|
<meta name="DC.Relation" scheme="URI" content="rzamzconfigssomgtcentral.htm" />
|
|
<meta name="DC.Relation" scheme="URI" content="rzamzenablessoisv.htm" />
|
|
<meta name="copyright" content="(C) Copyright IBM Corporation 2000, 2006" />
|
|
<meta name="DC.Rights.Owner" content="(C) Copyright IBM Corporation 2000, 2006" />
|
|
<meta name="DC.Format" content="XHTML" />
|
|
<meta name="DC.Identifier" content="rzamzscenarios" />
|
|
<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>Scenarios</title>
|
|
</head>
|
|
<body id="rzamzscenarios"><a name="rzamzscenarios"><!-- --></a>
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
|
<h1 class="topictitle1">Scenarios</h1>
|
|
<div><p>Use this information to review scenarios that illustrate
|
|
typical single signon implementation situations to help you plan your own
|
|
certificate implementation as part of your server security policy.</p>
|
|
<p>These scenarios provide a logical progression for configuring and using
|
|
single signon in an enterprise. Although all of these scenarios provide models
|
|
for network administrators, there is also a scenario for application developers
|
|
that demonstrates the tasks that a developer needs to complete to create applications
|
|
that can participate in a single signon environment.</p>
|
|
</div>
|
|
<div>
|
|
<ul class="ullinks">
|
|
<li class="ulchildlink"><strong><a href="rzamzenablesso.htm">Scenario: Create a single signon test environment</a></strong><br />
|
|
In this scenario, you want to configure network authentication service and EIM to create a basic single signon test environment. Use this scenario to gain a basic understanding of what configuring a single signon environment involves on a small scale before implementing single signon across an entire enterprise.</li>
|
|
<li class="ulchildlink"><strong><a href="rzamzenablessoos400.htm">Scenario: Enable single signon for i5/OS</a></strong><br />
|
|
View this scenario to learn how to configure network authentication service and EIM to create a single signon environment across multiple systems in an enterprise. This scenario expands on the concepts and tasks presented in the previous scenario which demonstrates how to create a simple single signon test environment.</li>
|
|
<li class="ulchildlink"><strong><a href="rzamzsynchconfig.htm">Scenario: Propagate network authentication service and EIM across multiple systems</a></strong><br />
|
|
This scenario demonstrates how to use the Synchronize Functions wizard in iSeries™ Navigator to propagate a single signon configuration across multiple systems in a mixed OS/400® release environment. Administrators can save time by configuring single signon once and propagating that configuration to all of their systems, instead of configuring each system individually.</li>
|
|
<li class="ulchildlink"><strong><a href="rzamzconfigssomgtcentral.htm">Scenario: Configure the Management Central servers for single signon</a></strong><br />
|
|
View this scenario to learn how to configure your Management Central servers to participate in a single signon environment. After administrators complete the scenario for propagating a single signon configuration across multiple systems, they can do the necessary configuration so that their Management Central servers can participate in the single signon environment.</li>
|
|
<li class="ulchildlink"><strong><a href="rzamzenablessoisv.htm">Scenario: Enable single signon for ISV applications</a></strong><br />
|
|
View this information to review scenarios that illustrate typical single signon implementation situations to help you plan your own certificate implementation as part of your server security policy.</li>
|
|
</ul>
|
|
|
|
<div class="familylinks">
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="rzamzsso.htm">Single signon</a></div>
|
|
</div>
|
|
</div>
|
|
</body>
|
|
</html> |