[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Condor-users] condor_hold authentication error

Hi Zachary,

Perhaps condor_hold doesn't check the AUTHENTICATION_METHODS variable??

I added AUTHENTICATION_METHODS=CLAIMTOBE to the condor config file for my central manager and the client machines. Then i shutdown all teh condor daemons and started them again on both machines.

The Linux central server (Condor 6.7.1) still complains "AUTHENTICATE:1003:Failed to authenticate with any method" when i try to issue a condor_hold on a job which was submitted by my Windows XP client (Condor 6.7.1). The hold command line looks like this "condor_hold -name thunder 40" .

Thanks for any tips, JW

Zachary Miller wrote:

On Wed, Sep 01, 2004 at 08:07:05PM -0700, John Wheez wrote:

AUTHENTICATE:1003:Failed to authenticate with any method

I'm using Linux condor-6.7.1 on my central manager and Condor 6.7.1 on my Windows XP clients.

If i am logged on the linux box as the condor user which has superuser status in my condor config for all machines and i try to place a job on hold which was submit from a Windows XP client I get the above error. If I go to the windows XP client and issue condor_hold it works fine. My condor user is locally on both machines and uses the same passwords.

unfortunately, this won't work right now. the reason is that by default there are no methods of authentication in common between unix and windows, and putting a job on hold requires authentication.

My windows machines do not get their login information from NIS. If I use NIS would this clear up the Authentication problem?


however, if you don't care about authentication but just want this to work, you
can add the CLAIMTOBE authentication method to both the windows and linux.  or
if you do care about authentication, you'll have to wait until we finish adding
kerberos or GSI authentication to the windows version.