From: Jeffrey Altman Date: Tue, 19 Jan 2010 03:23:54 +0000 (-0500) Subject: Windows: Help text update for Network Identity Manager Provider X-Git-Tag: openafs-devel-1_5_69^0 X-Git-Url: https://git.openafs.org/?p=openafs.git;a=commitdiff_plain;h=340d3be82aa6d1fbaa0c775fe743f86e5a7335ed Windows: Help text update for Network Identity Manager Provider Update the NetIdMgr provider help text to better describe its functionality. (Or at least not be incorrect.) Change-Id: I5d6b18f15cab7c48751666e754223ee68fb18d11 Reviewed-on: http://gerrit.openafs.org/1124 Reviewed-by: Jeffrey Altman Tested-by: Jeffrey Altman --- diff --git a/src/WINNT/netidmgr_plugin/help/html/bugs.htm b/src/WINNT/netidmgr_plugin/help/html/bugs.htm index 214215c..064229a 100644 --- a/src/WINNT/netidmgr_plugin/help/html/bugs.htm +++ b/src/WINNT/netidmgr_plugin/help/html/bugs.htm @@ -10,8 +10,8 @@

Reporting Bugs and Requesting Features

If you experience a bug in the program, please send email to bugs@secure-endpoints.com and report it. Please +href="mailto:openafs-bugs@openafs.org" +class="mail">openafs-bugs@openafs.org and report it. Please include as much information as possible to enable us to reproduce the problem.

diff --git a/src/WINNT/netidmgr_plugin/help/html/copyright.htm b/src/WINNT/netidmgr_plugin/help/html/copyright.htm index 2d63278..e471cff 100644 --- a/src/WINNT/netidmgr_plugin/help/html/copyright.htm +++ b/src/WINNT/netidmgr_plugin/help/html/copyright.htm @@ -22,7 +22,7 @@ the same appear on ALL copies of the software and documentation, including modifications that you make for internal use or for distribution:

-

Copyright 2005 by Secure Endpoints Inc.. All rights reserved.

+

Copyright 2005-2009 by Secure Endpoints Inc.. All rights reserved.

THIS SOFTWARE IS PROVIDED "AS IS", AND SECURE ENDPOINTS INC. MAKES NO REPRESENTATIONS OR WARRANTIES, EXPRESS OR IMPLIED. By way of diff --git a/src/WINNT/netidmgr_plugin/help/html/token_methods.htm b/src/WINNT/netidmgr_plugin/help/html/token_methods.htm index 7d163d6..e7192a4 100644 --- a/src/WINNT/netidmgr_plugin/help/html/token_methods.htm +++ b/src/WINNT/netidmgr_plugin/help/html/token_methods.htm @@ -9,10 +9,10 @@

Token Acquisition Methods

-

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. +

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.

Contents

@@ -46,13 +46,12 @@ resulting Kerberos 4 ticket is used to construct the AFS token. 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. -

+ticket) will not be available to obtain the service ticket with.

Automatic method selection

-

When the OpenAFS plug-in is configured to use automatic method +

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 @@ -63,8 +62,8 @@ used for all methods. 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. -

+explicitly.  Contact your AFS cell administrator to find out which token +acquisition methods are supported.

\ No newline at end of file diff --git a/src/WINNT/netidmgr_plugin/help/html/tokens_per_id.htm b/src/WINNT/netidmgr_plugin/help/html/tokens_per_id.htm index ec14f2f..aefb2ef 100644 --- a/src/WINNT/netidmgr_plugin/help/html/tokens_per_id.htm +++ b/src/WINNT/netidmgr_plugin/help/html/tokens_per_id.htm @@ -1,37 +1,36 @@ - Configuring identifications to obtain tokens for AFS cells + Configuring Network Identities to obtain tokens for AFS cells -

Configuring identifications to obtain tokens for AFS cells

+

Configuring Network Identities to obtain tokens for AFS cells

-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 Token Aquisition Methods topic). -

+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 Token Aquisition Methods topic.

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.

Specifying AFS cells when obtaining new credentials

-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).

New credentials window showing AFS cells in the credentials summary window

@@ -48,19 +47,18 @@ class="pre">AFS button at the bottom of the expanded dialog.

AFS identification options page

-

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 +

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 Obtain AFS -tokens checkbox, you can prevent AFS tokens from being obtained -for this idenfication. +tokens checkbox, you prevent AFS tokens from being obtained +for this identity.

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 Changing persistent tokent lists). +panels. (See Changing persistent token lists).

To add a cell:

@@ -72,17 +70,15 @@ text box.
  • Specify the Kerberos realm for the service ticket in the Realm text box. Note that you can select (Automatic) 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 (Automatic) 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 Realm as (Automatic)
  • Specify the token acquisition method in the Method. You can select (Automatic) 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) 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 Token Acquisition Methods topic.
  • @@ -93,14 +89,14 @@ cell.

    Note that only one token can exist per cell per login session. -Which means that if you already have a token for cell X while -you are logged in as user A, then you can't have another -token for cell X. This means that only one identification can -obtain a token for a given cell.

    - -

    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 X while +logged in as user A, 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.

    + +

    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:

    @@ -108,9 +104,9 @@ warning such as the following: Message displaying warning about a duplicate cell

    -

    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 +

    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.

    @@ -167,23 +163,23 @@ prompt indicating what the problem is.

    -

    Changing persistent cell lists for existing identifications

    +

    Changing persistent cell lists for existing identities

    -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 Apply and you are done.

    -

    The AFS configuration panel for an identification is shown below.

    +

    The AFS configuration panel for an identity is shown below.

    You can reach this configuration panel by opening the configuration -dialog (Options menu), and then clicking the -persistent identification you need to modify options for.

    +dialog (Options menu), and then clicking the persistent +identity you wish to modify options for.

    \ No newline at end of file diff --git a/src/WINNT/netidmgr_plugin/help/html/welcome.htm b/src/WINNT/netidmgr_plugin/help/html/welcome.htm index 592b13a..b728658 100644 --- a/src/WINNT/netidmgr_plugin/help/html/welcome.htm +++ b/src/WINNT/netidmgr_plugin/help/html/welcome.htm @@ -6,21 +6,22 @@ -

    Welcome to the OpenAFS plug-in for NetIDMgr

    +

    Welcome to the Network Identity Manager OpenAFS Provider

    -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.

    -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 http://www.secure-endpoints.com +href="http://www.openafs.org/windows.html">http://www.openafs.org/windows.html for updates.

    @@ -29,13 +30,12 @@ for updates.
  • Reporting problems and requesting features
  • -

    Using the OpenAFS plug-in

    +

    Using the OpenAFS Provider