condor_store_cred
add
[
-c | -u username
]
[-p password]
[-n machinename]
[-f filename]
condor_store_cred
delete
[
-c | -u username
]
[-n machinename]
condor_store_cred
query
[
-c | -u username
]
[-n machinename]
On a Windows machine, condor_store_cred stores the password of a user/domain pair securely in the Windows registry. Using this stored password, Condor is able to run jobs with the user ID of the submitting user. In addition, Condor uses this password to acquire the submitting user's credentials when writing output or log files. The password is stored in the same manner as the system does when setting or changing account passwords. When condor_store_cred is invoked, it contacts the condor_schedd daemon to carry out the requested operations on behalf of the user. This is necessary since registry keys are accessible only by the Windows SYSTEM account, not by administrators or other users.
On a Unix machine, condor_store_cred is used to manage the pool password, placed in a file specified by the SEC_PASSWORD_FILE configuration variable, and for use in password authentication among Condor daemons.
The password is stashed in a persistent manner; it is maintained across system reboots.
The add argument stores the current user's password securely in the registry. The user is prompted to enter the password twice for confirmation, and characters are not echoed. If there is already a password stashed, the old password will be overwritten by the new password.
The delete deletes the current password, if it exists.
The query reports whether the password is stored or not.
condor_store_cred will exit with a status value of 0 (zero) upon success, and it will exit with the value 1 (one) upon failure.
See the Condor Version 7.2.4 Manual or http://www.condorproject.org/license for additional notices.