Hoping someone can help me out.
I have a script in JAMF that is very simple and runs the KLIST command only.
#!/bin/bash
klist
exit 0
When run on a machine with valid kerberos ticket I get a klist: Cache not found: error. Wehn I run this script in a terminal window with sudo I get valid results. Not sure ehy running it thru JAMF is returning an error.
Thank you in advance.
+16I don’t know what specifically is happening here as I am not that familiar with Kerberos anymore, but several things are different in the environment between running a script in Terminal and Jamf running it as a policy. Environment variables, PATH settings, and several others. I notice that the cache is a parameter in the klist command, maybe it is looking for it in the wrong place due to the different environment. Does a user session need to be established? I know I am asking more questions than I am answering, but these are all things that can cause the kind of different behavior from a script. We’ve been bitten by this more than once in the past, and probably will continue to see it in the future...
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.