Re: [Condor-users] New feature request: condor_store_cred verify

[matthew hope <matthew.hope@xxxxxxxxx>]

on a similar vein - if somes credentials are wrong when running a job
could that please force the job to go on hold rather than bouncing
across all machines repeatedly...

On Mon, 29 Nov 2004 12:50:15 -0700, bgore@xxxxxxxxxx <bgore@xxxxxxxxxx> wrote:
> I second that request. ~B
> 
> 
> 
> -----Original Message-----
> From: condor-users-bounces@xxxxxxxxxxx [mailto:condor-users-bounces@xxxxxxxxxxx] On Behalf Of Ian Chesal
> Sent: Monday, November 29, 2004 12:25 PM
> To: Condor-Users Mail List; condor-admin@xxxxxxxxxxx
> Subject: [Condor-users] New feature request: condor_store_cred verify
> 
> The scenario: user changes their NT password and then forgets to run condor_store_cred delete/add to update the stored credentials. The trouble arises when a scripted interface to condor uses "condor_store_cred query" to ensure the user has stored their credentials -- it returns true if the credentials are stored, even if they are stale. It would be useful to either augment the query argument or add a verify argument to condor_store_cred that checks the stored credentials to make sure a user's credentials that are stored work.
> 
> Currently users see errors in their shadow.log file if their credentials aren't working. I don't want to have to educate my users on Condor log file analysis.
> 
> Seems like a trivial thing to check that the stored credentials function properly on-demand like this.
> 
> Ian
> 
> --
> Ian R. Chesal <ichesal@xxxxxxxxxx>
> Senior Software Engineer
> 
> Altera Corporation
> Toronto Technology Center
> Tel: (416) 926-8300
> 
> _______________________________________________
> Condor-users mailing list
> Condor-users@xxxxxxxxxxx http://lists.cs.wisc.edu/mailman/listinfo/condor-users
> 
> _______________________________________________
> Condor-users mailing list
> Condor-users@xxxxxxxxxxx
> http://lists.cs.wisc.edu/mailman/listinfo/condor-users
>