Challenge-Handshake Authenticate Protocol (Chap) - Chelsio Communications Terminator Series Installation And User Manual

Chapter X. iSCSI PDU Offload Target
# ACL configuration
#
# initiator "iqn.2006-02.com.chelsio.san1" is allowed full access
# to this target
ACL=iname=iqn.2006-02.com.chelsio.san1
# any initiator from IP address 102.50.50.101 is allowed full
access
ACL=sip=102.50.50.101
# any initiator connected via the target portal 102.60.60.25
is # allowed full access to this target
ACL=dip=102.60.60.25
# initiator "iqn.2005-09.com.chelsio.san2" from 102.50.50.22 and
# connected via the target portal 102.50.50.25 is allowed read
only # access of this target
ACL=iname=iqn.2006-
02.com.chelsio.san2;sip=102.50.50.22;dip=102.50.50.25;lun=ALL:R
4.5.

Challenge-Handshake Authenticate Protocol (CHAP)

CHAP is a protocol that is used to authenticate the peer of a connection and uses the notion of a
challenge and response, (i.e., the peer is challenged to prove its identity).
The Chelsio iSCSI software supports two CHAP methods: one-way and mutual. CHAP is
supported for both login and discovery sessions.
Normal Session CHAP Authentication
For a normal Session, the CHAP authentication is configured on a per-target basis.
Oneway CHAP Authentication
With one-way CHAP (also called unidirectional CHAP) the target uses CHAP to authenticate the
initiator. The initiator does not authenticate the target. This method is the default method.
For one-way CHAP, the initiator CHAP id and secret are configured and stored on a per-initiator
with Chelsio Entity parameter "Auth_CHAP_Initiator".
Mutual CHAP Authentication
With mutual CHAP (also called bidirectional CHAP), the target and initiator use CHAP to
authenticate each other.
Chelsio Unified Wire for Linux
# of this target
170