Subject: Re: [HTCondor-users] Multiple CredDs in a single pool
On 12/21/2022 8:26 AM, Miguel Garrido
wrote:
We already use CREDD_CACHE_LOCALLY in our pool, however, I'm not sure
how long the cache is good for. I want to make sure I can survive at
least one CREDD failure without much delay/interruption in a scenario
where the local cache is invalid,
Hi Miguel,
With CREDD_CACHE_LOCALLY=True in a MS Windows environment with the
HTCondor running as a service, anytime an HTCondor daemon
successfully fetches login info from the central CREDD it will store
it on the local machine (in the secure area of the registry). After
that, HTCondor will always first try to use the login info from the
local cached copy. If an attempt to login a user using a cached
credential fails (perhaps because the user changed their password,
etc), HTCondor will attempt to pull a fresh copy from the CREDD. If
I recall correctly, it will only replace the cached copy if/when it
successfully pulls a new copy from the CREDD.