<h1>Token Acquisition Methods</h1>
-<p>AFS tokens can be obtained via several different methods. Each of
-the methods that are natively supported by the OpenAFS plug-in is
-described below. Note that, additional plug-ins may define other
-acquisition methods that are not listed here.
+<p>AFS tokens can be obtained via several different methods. Each of the methods
+that are natively supported by the OpenAFS provider is described below. Note
+that the OpenAFS provider is extensible and other
+acquisition methods may be available other than those listed here.
</p>
<h4>Contents</h4>
to construct the AFS token. In order to use this method, the identity
must be be configured to obtain Kerberos 4 tickets when obtaining and
renewing credentials. Otherwise a Kerberos 4 TGT (ticket granting
-ticket) will not be available to obtain the service ticket with.
-</p>
+ticket) will not be available to obtain the service ticket with.</p>
<a name="auto"/>
<h3>Automatic method selection</h3>
-<p>When the OpenAFS plug-in is configured to use automatic method
+<p>When the OpenAFS provider is configured to use automatic method
selection for obtaining an AFS token, it iterates through the Kerberos
5, Kerberos 524 and Kerberos 4 methods until one of them succeeds. If
a realm for the service ticket is specified, then the realm will be
configuration of the AFS cell and the associated Kerberos realm. In
most cases, automatic method selection will determine the correct
realm. However, other cases, the method will have to be specified
-explicitly.
-</p>
+explicitly. Contact your AFS cell administrator to find out which token
+acquisition methods are supported.</p>
</body>
</html>
\ No newline at end of file
<html>
<head>
- <title>Configuring identifications to obtain tokens for AFS cells</title>
+ <title>Configuring Network Identities to obtain tokens for AFS cells</title>
<meta name="description" content="Specifying tokens per identification">
<meta name="keywords" content="tokns, identification, specify">
<link rel="stylesheet" type="text/css" href="afsplhlp.css">
</head>
<body>
-<h1>Configuring identifications to obtain tokens for AFS cells</h1>
+<h1>Configuring Network Identities to obtain tokens for AFS cells</h1>
<p>
-The OpenAFS plug-in maintains a list of AFS cells for each identification.
+The OpenAFS Provider maintains a list of AFS cells for each network identity.
A list is created the first time AFS tokens are obtained for an
-identification or when the list of cells is
-specified in the identification configuration panels. Each AFS cell that
-is listed is associated with a method by which a token should
-be obtained and the name of the Kerberos realm that is used to
-obtain the service ticket (more details are provided in the <a
-href="token_methods.htm">Token Aquisition Methods</a> topic).
-</p>
+identity or when the list of cells is
+specified in the identity configuration panels. Each AFS cell that
+is listed has associated with it a token acquisition method and the name of the Kerberos realm
+from which the AFS service ticket can be obtained. More details are provided in the <a
+href="token_methods.htm">Token Aquisition Methods</a> topic.</p>
<p>The following sections detail the process by which AFS cells can be
-specified when obtaining new credentials or configuring identifications.
+specified when obtaining new credentials or configuring identities.
</p>
<a name="new_tokens" />
<h3>Specifying AFS cells when obtaining new credentials</h3>
<p>
-When the OpenAFS plug-in is installed, it enhances the NetIDMgr new credentials
+When the OpenAFS Provider is installed, it enhances the Network Identity Manager
+"New Credentials"
dialog with an AFS tokens options panel. A typical new
credentials dialog is shown below demonstrating AFS cells listed in the
-credentials summary window.
+credentials summary window (Network Identity Manager version 1.2).
</p>
<p><img src="images/window_nc_main.bmp" alt="New credentials window showing AFS cells in the credentials summary window" /></p>
<p><img src="images/window_nc_afs_0.bmp" alt="AFS identification options page" /></p>
-<p>This page allows you to specify if AFS tokens are obtained for this
-identification and if so, for which tokens and by which method will they be
+<p>This page allows you to specify if AFS tokens are obtained for this identity and if so, for which tokens and by which method will they be
obtained. By unchecking the <span class="pre">Obtain AFS
-tokens</span> checkbox, you can prevent AFS tokens from being obtained
-for this idenfication.
+tokens</span> checkbox, you prevent AFS tokens from being obtained
+for this identity.
</p>
<p>Once the new credentials dialog successfully completes, the list of
-cells will be saved with the identification. The next
-time you obtain new credentials for the identification, the list of cells
+cells will be saved with the identity. The next
+time you obtain new credentials for the identity, the list of cells
will be loaded automatically. This list can be edited either by using
the new credentials dialog or the identity configuration
-panels. (See <a href="#persistent_tokens">Changing persistent tokent lists</a>).
+panels. (See <a href="#persistent_tokens">Changing persistent token lists</a>).
</p>
<h4>To add a cell:</h4>
<li>Specify the Kerberos realm for the service ticket in the <span
class="pre">Realm</span> text box. Note that you can select <span
-class="pre">(Automatic)</span> as the realm to allow the OpenAFS
-plug-in to select the realm. For most cases, you don't need to specify
-the realm manually and can safely leave the <span
+class="pre">(Automatic)</span> as the realm to allow the OpenAFS provider to select the realm. For most cases, you don't need to specify
+the realm manually and can simply leave the <span
class="pre">Realm</span> as <span class="pre">(Automatic)</span></li>
<li>Specify the token acquisition method in the <span
class="pre">Method</span>. You can select <span
-class="pre">(Automatic)</span> as the method to allow the OpenAFS
-plug-in to select the method automatically. Similar to the automatic
-realm selection, for most cases the plug-in will be able to correctly
-select the token aquisition method. More details about credentials
+class="pre">(Automatic)</span> as the method to allow the OpenAFS provider to select the method automatically. Similar to the automatic
+realm selection, for most cases the provider will be able to correctly
+select the token acquisition method. More details about credentials
acquisition methods are provided in the <a
href="token_methods.htm">Token Acquisition Methods</a> topic.</li>
</p>
<p>Note that only one token can exist per cell per login session.
-Which means that if you already have a token for cell <em>X</em> while
-you are logged in as user <em>A</em>, then you can't have another
-token for cell <em>X</em>. This means that only one identification can
-obtain a token for a given cell.</p>
-
-<p>Therefore, if you try to add a cell to an identification which is
-already listed in the persistent cell list for another identification or
-which currently exists under a different identification, you will receive a
+If a token exists for cell <em>X</em> while
+logged in as user <em>A</em>, then any attempt to obtain credentials for cell X
+as user B will result in the loss of the previous token. Only one identity can
+posses a token for a given cell at a time.</p>
+
+<p>Therefore, if you try to add a cell to an identity which is already listed in
+the persistent cell list for another identity or
+which currently exists under a different identity, you will receive a
warning such as the following:
</p>
<img src="images/window_nc_prob.bmp" alt="Message displaying warning about a duplicate cell" />
</p>
-<p>From here, you can decide to keep the cell listed for both
-identifications (although only one of them can be active at any given
-time), or remove the cell from all the other identifications and add it to
+<p>From here, you can decide to keep the cell listed for both identity (although
+only one of them can be active at any given time), or remove the cell from all
+the other identity and add it to
the current one. Also, you can cancel the add cell request.
</p>
</p>
<a name="persistent_tokens" />
-<h3>Changing persistent cell lists for existing identifications</h3>
+<h3>Changing persistent cell lists for existing identities</h3>
<p>
-The configuration panel for a persistent identification contains a panel for
+The configuration panel for a persistent identity contains a panel for
specifying the AFS cells. This panel is identical to the panel used
by the new credentials dialog. You can easily modify the cell lists
as described above and click <span class="pre">Apply</span> and you
are done.
</p>
-<p>The AFS configuration panel for an identification is shown below.</p>
+<p>The AFS configuration panel for an identity is shown below.</p>
<p><img src="images/window_cfg_afs_0.bmp" /></p>
<p>You can reach this configuration panel by opening the configuration
-dialog (<span class="pre">Options</span> menu), and then clicking the
-persistent identification you need to modify options for.</p>
+dialog (<span class="pre">Options</span> menu), and then clicking the persistent
+identity you wish to modify options for.</p>
</body>
</html>
\ No newline at end of file
<link rel="stylesheet" type="text/css" href="afsplhlp.css">
</head>
-<h1>Welcome to the OpenAFS plug-in for NetIDMgr</h1>
+<h1>Welcome to the Network Identity Manager OpenAFS Provider</h1>
<img src="images/openafs-logo.jpg"/>
<p>
-The OpenAFS plug-in extends the Network Identity Manager (or
-NetIDMgr for short) to support AFS credential management. This plug-in
-obtains AFS tokens for the cells associated with each identification
+The OpenAFS Provider extends the Network Identity Manager (or
+NetIDMgr for short) to support AFS credential management. This Provider
+obtains AFS tokens for the cells associated with each identity
and provides the tools necessary to maintain them.
</p>
<p>
-This version of the plug-in is provided by Secure Endpoints Inc.
+This version of the provider is distributed by OpenAFS as part of OpenAFS for
+Windows.
Visit <a class="external"
-href="http://www.secure-endpoints.com">http://www.secure-endpoints.com</a>
+href="http://www.openafs.org/windows.html">http://www.openafs.org/windows.html</a>
for updates.
</p>
<li><a href="bugs.htm">Reporting problems and requesting features</a></li>
</ul>
-<h3>Using the OpenAFS plug-in</h3>
+<h3>Using the OpenAFS Provider</h3>
<ul>
<li>
-<a href="tokens_per_id.htm">Associating an AFS cell with an
-identification</a>: How to configure identification options to obtain
+<a href="tokens_per_id.htm">Associating an AFS cell with an identity</a>: How to configure identity options to obtain
tokens for select AFS cells.</li>
<li>
<h3>External links</h3>
<ul>
-<li><a class="external" href="http://openafs.org">http://openafs.org</a>:
+<li><a class="external" href="http://www.openafs.org">http://www.openafs.org</a>:
OpenAFS
</li>
git://git.openafs.org / openafs.git / commitdiff