HELP! How to cache credentials?? RRS feed

  • Question

  • I am using HPC 2008 R2.  I opened a power shell on the head node and typed the following:

    hpccred setcreds /scheduler:xyz123 /user:myname /password:mypass 

    Upon hitting enter I didn't receive any error.  When I try to run a job from my desktop via the debugger in Visual Studio 2010 It stops at the point where the password is needed.  I am supplying the username via the code, but I have the password parameter set to null --> scheduler.SubmitJob(myJob, username, null);

    Am I setting the credentials correctly?  If I am not how do I set the users credentials via the power shell?  I would like to do this so that the user doesn't have to enter a password every time they submit a job.

    Friday, September 7, 2012 8:19 PM

All replies

  • is the username you used in SubmitJob() the same as you used in "hpccred /user:myname"?

    have you tried to submit a job through hpc job manager?

    Sunday, September 9, 2012 3:23 PM
  • btw, which SP of HPC 2008 R2 are you using?
    Sunday, September 9, 2012 3:23 PM
  • Yes, I used the same username.  I am using SP4.  Wondering if the syntax is correct?

    I am able to submit a job through the job manager OK.  

    Sunday, September 9, 2012 4:37 PM
  • When you said that "It stops at the point where the password is needed.  " do you mean that you get a prompt for a password ?

    Is there any chance that the powershell and visual studio are running as different users ?

    Thursday, September 13, 2012 4:09 PM
  • Hi, I am also facing the same issue.  Can anyone help me on this..

    I have tried using cluscfg setcreds / hpccred setceds.. But no luck... I am running the commands on head node .. upon trigger of the job it moving into "Configuring" status and hangs... 

    • Edited by DhanunjayaC Tuesday, October 16, 2012 9:29 PM
    Tuesday, October 16, 2012 9:26 PM
  • For this scheduler.SubmitJob(myJob, username, null);

    try to set username to null?

    Tuesday, October 16, 2012 9:55 PM
  • Hi Mike,

    We are using cluster.SubmitJob(Jobid, Username, string.empty,false,0) in the logic.

    Here the username is configurbale and userid  changes from Job to Job depending on Jobtype.  Anyway I have set the Username & Pwd to NULL .

    But still the jobs are hanging in Configuring status...

    Tuesday, October 16, 2012 10:35 PM
  • hmm.... under which user is that job submit running as? Can you try running it under admin account? I'm just suggesting different things to try out here to gain a better understanding of the problem.


    Tuesday, October 16, 2012 10:56 PM
  • If it is any help, I am using the line scheduler.SubmitJob(myJob, username, null);

    Where I was having an issue was with other users caching their credentials.  I figured this out.

    You may also want to try this - I had everyone open a power shell and submit their credentials that way so they were cached on the server.  Then you can use the null without any issues as "I think" by default if you have set user and password to null it will look in the cache for the credentials based on who submitted the job.

    Wednesday, October 17, 2012 1:21 PM