See Gnats PR 602 for a description of this documentation request, and the required Stork installation steps. -Configuring, Using Stork + Condor Credd [Carey's credd, not GreqQ's credd]: +Configuring, Using Stork + HTCondor Credd [Carey's credd, not GreqQ's credd]: Note: all references below are to the "old" condor_credd, aka the Stork credential management daemon. The fact that we now have 2 distinct credential @@ -65,7 +65,7 @@ # condor_config_val DAEMON_LIST DAEMON_LIST: COLLECTOR, CREDD, MASTER, NEGOTIATOR, SCHEDD, STARTD, STORK -Start Condor, including Stork, CredD: +Start HTCondor, including Stork, CredD: # condor_master Using Stork: See tutorial: @@ -160,9 +160,9 @@ 1) Carey did it. ;-) This code and reasoning predated Jeff. -2). Jeff can infer that the condor_credd was intended to be a Condor daemoncore +2). Jeff can infer that the condor_credd was intended to be a HTCondor daemoncore generic credential management daemon, and was intended to manage a wide variety -of credentials, including X.509 proxies, and using the daemoncore API. Condor +of credentials, including X.509 proxies, and using the daemoncore API. HTCondor daemoncore clients to the condor_credd only had to retrieve credentials from the [Stork] condor_credd, and did not have to know or care that the condor_credd used MyProxy behind the scenes to refresh X.509 credentials.
