Re: [PATCH v3 0/3] target: iscsi: control authentication per ACL

[Mike Christie <michael.christie@oracle.com>]

On 5/4/22 1:02 PM, Dmitriy Bogdanov wrote:
> Hi Mike,
> 
> I've just tried one more time to reproduce your error and I failed again.
> With your config file the behavior is the absolutely the same for both cases with my patchset and without my patchset: 
> * for dynamic ACLs - target fails the login and shows the bellow logs.
> * for the registered ACL - target succeeds the login.
> 
> Could you, please, re-check the patchset?

Sorry I missed your reply at the bottom and sorry I messed up
somewhere while testing the patches. I can't replicate the issue
I thought I hit and yeah I agree the config file I attached in
the last mail didn't make sense.

The patches look ok, but you need to rebase them.


> 
> BR,
>  Dmitry
> 
> -----Original Message-----
> From: Dmitriy Bogdanov <d.bogdanov@yadro.com> 
> Sent: Friday, October 22, 2021 10:48 AM
> To: Mike Christie <michael.christie@oracle.com>; Martin Petersen <martin.petersen@oracle.com>; target-devel@vger.kernel.org
> Cc: linux-scsi@vger.kernel.org; linux@yadro.com
> Subject: RE: [PATCH v3 0/3] target: iscsi: control authentication per ACL
> 
> Hi Mike,
> 
>> I can't seem to get the patches working with the targetcli config file below It worked ok before the patches.
>>
>> I get this error:
>>
>> Oct 22 00:56:25 ol4 kernel: CHAP user or password not set for Initiator ACL
>> Oct 22 00:56:25 ol4 kernel: Security negotiation failed.
>> Oct 22 00:56:25 ol4 kernel: iSCSI Login negotiation failed.
> 
> This kind of error is reported for the unknown (dynamic) ACL since the config file have not have
> userid/password configured for TPG. Your config file looks strange - it has generate_dyn_acls=1
> but has not credentials for dynamic acls.
> 
> Login from the configured ACL in this config file works well for me.
> 
> Could you, please, describe more details of your usecase?
> 
> BR,
>  Dmitry