You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We're running RunDeck in Linux using a service account. This means any kinit run is cached in the same file location (currently /tmp/krb5cc_UID) with the service accounts UID in the file name. If several Jobs were run at the same time there is a problem with the cache content.
Error: Can't find client principal @ in cache collection"
I've tried to include the RunDeck job username into the cache file path but I couldn't make it working. I've also tried to use the '-c' command line option for kinit in the plugin configuration what ended also in a not working kerberos authentication. I couldn't find any further documentation about how to configure kinit in the plugin settings properly.
Can you please help?
br,
Mathias
The text was updated successfully, but these errors were encountered:
Hi,
We're running RunDeck in Linux using a service account. This means any kinit run is cached in the same file location (currently /tmp/krb5cc_UID) with the service accounts UID in the file name. If several Jobs were run at the same time there is a problem with the cache content.
Error: Can't find client principal @ in cache collection"
I've tried to include the RunDeck job username into the cache file path but I couldn't make it working. I've also tried to use the '-c' command line option for kinit in the plugin configuration what ended also in a not working kerberos authentication. I couldn't find any further documentation about how to configure kinit in the plugin settings properly.
Can you please help?
br,
Mathias
The text was updated successfully, but these errors were encountered: