On Wed, Mar 3, 2010 at 8:12 AM, Chandra Seetharaman <sekharan@xxxxxxxxxx> wrote: > > > On Tue, 2010-03-02 at 21:50 +0100, Tomasz Chmielewski wrote: >> On 02.03.2010 01:35, Chandra Seetharaman wrote: >> > Looks like it will lead to confusion if we allow the account to be >> > defined at the target level. >> > >> > May be we should define the account (account name and password) at the >> > global level and have just the "association" at the target level, what >> > do you think ? >> >> Any recommendations for targets.conf format? >> > > At the global level, we could have > > user accountname1 password1 > user accountname2 password2 > : > : > : > and under target, > > incominguser accountname1 > outgoinguser accountname2 > > With the recent addition of discovery chap authentication, we need to > also add a "global-incominguser" and "global-outgoinguser", like > > global-incominguser accountname1 > global-outgoinguser accountname2 > > What do you think ? Comments anybody ? > > May be it should be discovery-incominguser instead of > global-incominguser ? Is it useful to have / allow different users for authentication for discovery vs normal login? If it is not, maybe keep incominguser/outgoinguser and have it apply to both logins and then add a new discovery-authentication = no|required to control if discovery sessions need authentication or not. > > Thanks, > > chandra > > >> > > -- > To unsubscribe from this list: send the line "unsubscribe stgt" in > the body of a message to majordomo@xxxxxxxxxxxxxxx > More majordomo info at http://vger.kernel.org/majordomo-info.html > -- To unsubscribe from this list: send the line "unsubscribe stgt" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
