Add description of incomingdiscoveryuser and outgoingdiscoveryuser to targets.conf.5. Update tgtadm.8 to remove a no-longer-true bit. Signed-off-by: Andy Grover <agrover@xxxxxxxxxx> --- doc/targets.conf.5.xml | 18 ++++++++++++++++++ doc/tgtadm.8.xml | 5 +---- 2 files changed, 19 insertions(+), 4 deletions(-) diff --git a/doc/targets.conf.5.xml b/doc/targets.conf.5.xml index f8abe20..f754df3 100644 --- a/doc/targets.conf.5.xml +++ b/doc/targets.conf.5.xml @@ -142,6 +142,24 @@ </listitem> </varlistentry> + <varlistentry><term><option>incomingdiscoveryuser <user> <userpassword></option></term> + <listitem> + <para> + Define iscsi incoming discovery authentication setting. If no + value is given, no authentication is performed. + </para> + </listitem> + </varlistentry> + + <varlistentry><term><option>outgoingdiscoveryuser <user> <userpassword></option></term> + <listitem> + <para> + Define iscsi outgoing discovery authentication setting. If no + value is given, no authentication is performed. + </para> + </listitem> + </varlistentry> + </variablelist> </refsect1> diff --git a/doc/tgtadm.8.xml b/doc/tgtadm.8.xml index ee973ba..668e184 100644 --- a/doc/tgtadm.8.xml +++ b/doc/tgtadm.8.xml @@ -572,12 +572,9 @@ tgtadm --op update --mode target --tid 1 -n DataDigest -v None <para> CHAP authentication is supported to require authentication before an initiator is allowed to log in and access devices. - TGTD supports setting CHAP for normal log in sessions only, not - for discovery sessions. Discovery sessions are always possible - without authentication. </para> <para> - CHAP authentication is set on the target level. + CHAP main-phase authentication is set on the target level. To set up CHAP authentication we first need to create an account and its associated password, then we bind the account to one or more targets. -- 1.7.1 -- To unsubscribe from this list: send the line "unsubscribe stgt" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html