From: Dmitriy Bogdanov <d.bogdanov@yadro.com>
To: Mike Christie <michael.christie@oracle.com>,
Martin Petersen <martin.petersen@oracle.com>,
"target-devel@vger.kernel.org" <target-devel@vger.kernel.org>
Cc: "linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>,
"linux@yadro.com" <linux@yadro.com>
Subject: RE: [PATCH v3 0/3] target: iscsi: control authentication per ACL
Date: Fri, 22 Oct 2021 07:48:07 +0000 [thread overview]
Message-ID: <15af5f6f490a42c5a02c9d9bd79f1a28@yadro.com> (raw)
In-Reply-To: <ec9e01a3-73d0-a06b-8c20-ae492c0c3313@oracle.com>
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
next prev parent reply other threads:[~2021-10-22 7:48 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-19 7:18 [PATCH v3 0/3] target: iscsi: control authentication per ACL Dmitry Bogdanov
2021-10-19 7:18 ` [PATCH v3 1/3] scsi: target: iscsi: Add upcast helpers Dmitry Bogdanov
2021-10-19 7:18 ` [PATCH v3 2/3] scsi: target: iscsi: extract auth functions Dmitry Bogdanov
2021-10-19 7:18 ` [PATCH v3 3/3] target: iscsi: control authentication per ACL Dmitry Bogdanov
2021-10-22 5:59 ` [PATCH v3 0/3] " Mike Christie
2021-10-22 7:48 ` Dmitriy Bogdanov [this message]
2022-05-04 18:02 ` Dmitriy Bogdanov
2022-05-10 19:38 ` Mike Christie
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=15af5f6f490a42c5a02c9d9bd79f1a28@yadro.com \
--to=d.bogdanov@yadro.com \
--cc=linux-scsi@vger.kernel.org \
--cc=linux@yadro.com \
--cc=martin.petersen@oracle.com \
--cc=michael.christie@oracle.com \
--cc=target-devel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox