Re: [HTCondor-users] Question about configuring a pool password

[Vladimir Brik <vladimir.brik@xxxxxxxxxxxxxxxx>]

> Also, I didn't mention that earlier because we were talking specifically
>  about PASSWORD, and you shouldn't be using PASSWORD for
>  user-to-daemon communications.  Thus, you don't want to require
>  PASSWORD using the SEC_DEFAULT_* mechanisms.
Do you mean it's not possible to use password authentication for 
user-to-daemon communications?


Vlad



On 11/16/16 12:55, Zach Miller wrote:
> > -----Original Message-----
> > From: Kandes, Martin
> > Sent: Wednesday, November 16, 2016 12:50 PM
> > To: HTCondor-Users Mail List <htcondor-users@xxxxxxxxxxx>
> > Subject: Re: [HTCondor-users] Question about configuring a pool password
> >
> > Zach,
> >
> > Okay, cool. Thanks. One last follow-up question then: Would you still have
> > to specify the SEC_NEGOTIATION_* options if you already have the
> > SEC_DEFAULT_* options specified? i.e., I assumed explicitly setting
> > SEC_DEFAULT_* would implicitly also set SEC_NEGOTIATION_*.
>
>
> SEC_DEFAULT_* is used if SEC_NEGOTIATION_* is not defined.  It's a fall-back, not an override.
>
> Also, I didn't mention that earlier because we were talking specifically about PASSWORD, and you shouldn't be using PASSWORD for user-to-daemon communications.  Thus, you don't want to require PASSWORD using the SEC_DEFAULT_* mechanisms.
>
> Hope that helps.
>
>
> Cheers,
> -zach
>
> _______________________________________________
> HTCondor-users mailing list
> To unsubscribe, send a message to htcondor-users-request@xxxxxxxxxxx with a
> subject: Unsubscribe
> You can also unsubscribe by visiting
> https://lists.cs.wisc.edu/mailman/listinfo/htcondor-users
>
> The archives can be found at:
> https://lists.cs.wisc.edu/archive/htcondor-users/