Return-Path: <owner-ips@ece.cmu.edu>
X-Sieve: cmu-sieve 2.0
Return-Path: <owner-ips@ece.cmu.edu>
Received: (from majordom@localhost)
	by ece.cmu.edu (8.11.0/8.10.2) id h0O225j07385
	for ips-outgoing; Thu, 23 Jan 2003 21:02:05 -0500 (EST)
X-Authentication-Warning: ece.cmu.edu: majordom set sender to owner-ips@ece.cmu.edu using -f
Received: from lion.ninthwonder.com (lion.ninthwonder.com [151.199.66.147])
	by ece.cmu.edu (8.11.0/8.10.2) with ESMTP id h0O223W07380
	for <ips@ece.cmu.edu>; Thu, 23 Jan 2003 21:02:03 -0500 (EST)
Received: by lion.ninthwonder.com (Postfix, from userid 1021)
	id 2E99E30706; Thu, 23 Jan 2003 21:01:42 -0500 (EST)
Date: Thu, 23 Jan 2003 17:56:27 -0800 (PST)
From: Bill Studenmund <wrstuden@wasabisystems.com>
X-X-Sender:  <wrstuden@candlekeep.home-net.internetconnect.net>
To: <ips@ece.cmu.edu>
Subject: ISCSI-MIB and AUTH-MIB question
Message-ID: <Pine.NEB.4.33.0301231750310.595-100000@candlekeep.home-net.internetconnect.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-ips@ece.cmu.edu
Precedence: bulk

In the ISCSI-MIB, we have a way to refer to entries in the AUTH-MIB that
may be used by the other side of a connection, using
iscsiIntrAuthorization and iscsiTgtAuthorization.

As I understand it, they are used for authenticating the other side of a
connection. Thus iscsiTgtAuthorization tells a target what auths (CHAP
secrets, etc.) an initiator can use to authenticate to it. Likewise as I
understand it, iscsiIntrAuthorization tells an initiator what auths to
require for mutual authentication.

How do we configure a device for the credentials it should use for its
half of authentication? i.e. how do we tell an initiator what CHAP secrets
it should use for its resposnes, and likewise how do we tell the target
what to use for mutual?

Take care,

Bill

