AWS Storage Gateway User Guide
Configuring CHAP Authentication
To set up mutual CHAP for your targets
1. Configure CHAP on the AWS Storage Gateway console, as discussed in
volume target on the AWS Storage Gateway console (p. 378)
.
2. In your client initiator software, complete the CHAP configuration:
• To configure mutual CHAP on a Windows client, see
To configure mutual CHAP on a Windows
• To configure mutual CHAP on a Red Hat Linux client, see
To configure mutual CHAP on a Red Hat
To configure CHAP for a volume target on the AWS Storage Gateway console
In this procedure, you specify two secret keys that are used to read and write to a volume. These same
keys are used in the procedure to configure the client initiator.
1. On the AWS Storage Gateway console, choose
Volumes
in the navigation pane.
2. On the
Actions
menu, choose
Configure CHAP Authentication
.
3. Provide the requested information in the
Configure CHAP Authentication
dialog box, shown in the
screenshot following:
a. For
Initiator Name
, type the name of your iSCSI initiator.
You can find the initiator name by using your iSCSI initiator software. For example, for
Windows clients, the name is the value on the
Configuration
tab of the iSCSI initiator. For more
information, see
To configure mutual CHAP on a Windows client (p. 380)
.
Note
To change an initiator name, you must first disable CHAP, change the initiator name in
your iSCSI initiator software, and then enable CHAP with the new name.
b. For
Secret used to Authenticate Initiator
, type the secret requested.
This secret must be a minimum of 12 characters and a maximum of 16 characters long. This
value is the secret key that the initiator (that is, the Windows client) must know to participate in
CHAP with the target.
c.
For
Secret used to Authenticate Target (Mutual CHAP)
, type the secret requested.
This secret must be a minimum of 12 characters and a maximum of 16 characters long. This
value is the secret key that the target must know to participate in CHAP with the initiator.
Note
The secret used to authenticate the target must be different than the secret to
authenticate the initiator.
API Version 2013-06-30
378