Here is the result of a "grep -i auth" on the level 9 debug output of iscsid on the client.
iscsid: updated 'node.session.auth.authmethod', 'None' => 'None' iscsid: updated 'node.session.auth.authmethod', 'None' => 'None' iscsid: updated 'node.conn[0].timeo.auth_timeout', '45' => '45' iscsid: updated 'node.session.auth.authmethod', 'None' => 'None' iscsid: authentication setup complete... iscsid: > AuthMethod=CHAP iscsid: Login failed to authenticate with target iqn.2010-01.com.example:storage.lun1 iscsid: session 1 login rejected: Initiator failed authentication with target
This confirms that the client indeed tries to authenticate using CHAP instead of None and doesn't respect its own configuration.
Here is the result of a "grep -i auth" on the level 9 debug output of iscsid on the client.
iscsid: updated 'node.session. auth.authmethod ', 'None' => 'None' auth.authmethod ', 'None' => 'None' 0].timeo. auth_timeout' , '45' => '45' auth.authmethod ', 'None' => 'None' 01.com. example: storage. lun1
iscsid: updated 'node.session.
iscsid: updated 'node.conn[
iscsid: updated 'node.session.
iscsid: authentication setup complete...
iscsid: > AuthMethod=CHAP
iscsid: Login failed to authenticate with target iqn.2010-
iscsid: session 1 login rejected: Initiator failed authentication with target
This confirms that the client indeed tries to authenticate using CHAP instead of None and doesn't respect its own configuration.