myproxy-admin-load-credential(8)

✨ myproxy-admin-load-credential ✨

ok so bestie, welcome to myproxy-admin-load-credential, part of the MyProxy manual set (section 8, admin girlies only πŸ’…). this one is a whole vibe and i'm gonna walk you through it like we're texting at 2am πŸ¦‹


🌸 NAME 🌸

myproxy-admin-load-credential β€” directly load repository πŸ’–


πŸŽ€ SYNOPSIS πŸŽ€

myproxy-admin-load-credential [ options ]

πŸ¦‹ DESCRIPTION πŸ¦‹

okay so here's the tea β˜• β€” the myproxy-admin-load-credential command stores a credential directly in the local MyProxy repository. it has to be run from the account that owns the repository, no exceptions bestie, it's giving "only the owner can touch this" energy πŸ‘‘

a lot of the options are lowkey similar to myproxy-init(1). BUT β€” and this is the main character plot twist β€” unlike myproxy-init, myproxy-admin-load-credential does not create a proxy from the source credential. instead it directly loads a copy of the source credential into the repository. like, a straight-up copy. no glow-up in between ✨

the pass phrase of the source credential is unchanged. so if you wanna switch it up after the credential is stored, use myproxy-admin-change-pass(8) β€” that's literally what it's for, iykyk 🫢

once it's in there, proxy credentials with a default lifetime of 12 hours can be retrieved by myproxy-logon(1) using the MyProxy passphrase. periodt πŸ’…

and the command's whole behavior? controlled by the following options, bestie. let's get into it ⬇️


✨ OPTIONS ✨

  • -h, --help β€” displays command usage text and exits. classic. πŸ™ˆ
  • -u, --usage β€” displays command usage text and exits. yes, again. it's a whole twin situation πŸ’€
  • -v, --verbose β€” enables verbose debugging output to the terminal. so much yapping, but make it useful πŸ”₯
  • -V, --version β€” displays version information and exits. the "who am i" moment πŸ’–
  • -s dir, --storage dir β€” specifies the location of the credential storage directory. the directory must be accessible only by the user running the myproxy-server process, for security reasons β€” like, this is not a drill, lock it down πŸ”’ Default: /var/lib/myproxy or /var/myproxy or $GLOBUS_LOCATION/var/myproxy
  • -c filename, --certfile filename β€” specifies the filename of the source certificate. this is a required parameter, bestie, no skipping it 🌸
  • -y filename, --keyfile filename β€” specifies the filename of the source private key. also required πŸ’… if the private key is encrypted, MyProxy clients will be required to give the encryption passphrase to access the key. when used with -R or -Z, it's common for the private key to not be encrypted, so MyProxy clients can access the credentials using only certificate-based authentication and authorization. so convenient, so iconic ✨
  • -l username, --username username β€” specifies the MyProxy account under which the credential should be stored. by default, the command uses the value of the LOGNAME environment variable. use this option to specify a different account username on the MyProxy server. and fun fact πŸ“ β€” the MyProxy username does not need to correspond to a real Unix username. fake it till you make it, bestie πŸ‘‘
  • -t hours, --proxy_lifetime hours β€” specifies the maximum lifetime of credentials retrieved from the myproxy-server(8) using the stored credential. Default: 12 hours ⏰
  • -d, --dn_as_username β€” use the certificate subject (DN) as the username. boom, identity ✨
  • -a, --allow_anonymous_retrievers β€” allow credentials to be retrieved with just pass phrase authentication. by default, only entities with credentials that match the myproxy-server.config(5) default retriever policy may retrieve credentials. this option lets entities without existing credentials retrieve a credential using pass phrase authentication, by including "anonymous" in the set of allowed retrievers. heads up though β€” the myproxy-server.config(5) server-wide policy must also allow "anonymous" clients for this option to actually have an effect. two keys, one door πŸšͺ
  • -A, --allow_anonymous_renewers β€” allow credentials to be renewed by any client. any client with a valid credential with a subject name that matches the stored credential may retrieve a new credential from the MyProxy repository if this option is given. since this effectively defeats the purpose of proxy credential lifetimes, it is not recommended. it is included only for sake of completeness. like, it's here, but it's not the vibe 😭
  • -r name, --retrievable_by name β€” allow the specified entity to retrieve credentials. see -x and -X options for controlling name matching behavior. πŸ‘€
  • -E name, --retrieve_key name β€” allow the specified entity to retrieve end-entity credentials. see -x and -X options for controlling name matching behavior. πŸ”‘
  • -R name, --renewable_by name β€” allow the specified entity to renew credentials. see -x and -X options for controlling name matching behavior. ♻️
  • -Z name, --retrievable_by_cert name β€” allow the specified entity to retrieve credentials without a passphrase. see -x and -X options for controlling name matching behavior. no passphrase?? slay πŸŽ€
  • -x, --regex_dn_match β€” specifies that names used with following options -r, -E, -R, and -Z will be matched against the full certificate subject distinguished name (DN) according to REGULAR EXPRESSIONS in myproxy-server.config(5). regex girlies rise 🧚
  • -X, --match_cn_only β€” specifies that names used with following options -r, -E, -R, and -Z will be matched against the certificate subject common name (CN) according to REGULAR EXPRESSIONS in myproxy-server.config(5). for example, if an argument of -r "Jim Basney" is specified, then the resulting policy will be "*/CN=Jim Basney". this is the default behavior. ⭐
  • -k name, --credname name β€” specifies the credential name. name it something cute πŸ’–
  • -K description, --creddesc description β€” specifies credential description. give it lore πŸ“

🫢 EXIT STATUS 🫢

  • 0 on success πŸŽ‰
  • >0 on error πŸ’€

πŸ‘‘ AUTHORS πŸ‘‘

See http://grid.ncsa.illinois.edu/myproxy/about for the list of MyProxy authors. the legends themselves, no cap πŸ’œ


🌈 SEE ALSO 🌈


ok that's the whole page bestie, you're officially certified πŸ’… this cutie came from the MyProxy crew and it's dated 2011-09-05 β€” yes, she's vintage, and she still ate πŸŽ€βœ¨

πŸ“¦ where this page comes from