delete the cache,remove the C:\Users\syssa2\AppData\Roaming\BladeLogic\blsesscc and then try to acquire the cred again.
Thanks Dhiraj for your response.
I am not familiar with the cache directory, do you mind telling me the path so I can delete the contents please?
And the problem is with BSA running non-interactive jobs (such as CLM's create user job). When you run such job from the BSA console (logged in as BLAdmins role, BLAdmin user), it still fails with this error.
So the question is, what sso cache file does BSA use in running such job when its not a user (such as Vinnie) running from the command line.
(Please note, when I run nsh from the app server in question, I dont have this issue )
1 of 1 people found this helpful
Shermeen / Vinnie, could it be a secure file configuration from where the problem occurs? Check c:\windows\rsc\secure on the server from where running nsh fails. Perhaps something is set incorrectly in that file? auth profile, etc..
It looks like I had to add the following:
' appserver_protocol=ssoproxy' to the secure file on the target server, and that seem to do the trick. No longer getting the error.
Thanks for your help everyone!