[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [HTCondor-users] Question about configuring a pool password
- Date: Wed, 16 Nov 2016 18:55:48 +0000
- From: Zach Miller <zmiller@xxxxxxxxxxx>
- Subject: Re: [HTCondor-users] Question about configuring a pool password
> -----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
> 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.