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 π-sdir,--storagedir β specifies the location of the credential storage directory. the directory must be accessible only by the user running themyproxy-serverprocess, for security reasons β like, this is not a drill, lock it down π Default:/var/lib/myproxyor/var/myproxyor$GLOBUS_LOCATION/var/myproxy-cfilename,--certfilefilename β specifies the filename of the source certificate. this is a required parameter, bestie, no skipping it πΈ-yfilename,--keyfilefilename β 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-Ror-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 β¨-lusername,--usernameusername β specifies the MyProxy account under which the credential should be stored. by default, the command uses the value of theLOGNAMEenvironment 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 π-thours,--proxy_lifetimehours β specifies the maximum lifetime of credentials retrieved from themyproxy-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 themyproxy-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 β themyproxy-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 π-rname,--retrievable_byname β allow the specified entity to retrieve credentials. see-xand-Xoptions for controlling name matching behavior. π-Ename,--retrieve_keyname β allow the specified entity to retrieve end-entity credentials. see-xand-Xoptions for controlling name matching behavior. π-Rname,--renewable_byname β allow the specified entity to renew credentials. see-xand-Xoptions for controlling name matching behavior. β»οΈ-Zname,--retrievable_by_certname β allow the specified entity to retrieve credentials without a passphrase. see-xand-Xoptions for controlling name matching behavior. no passphrase?? slay π-x,--regex_dn_matchβ specifies that names used with following options-r,-E,-R, and-Zwill be matched against the full certificate subject distinguished name (DN) according to REGULAR EXPRESSIONS inmyproxy-server.config(5). regex girlies rise π§-X,--match_cn_onlyβ specifies that names used with following options-r,-E,-R, and-Zwill be matched against the certificate subject common name (CN) according to REGULAR EXPRESSIONS inmyproxy-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. β-kname,--crednamename β specifies the credential name. name it something cute π-Kdescription,--creddescdescription β specifies credential description. give it lore π
π«Ά EXIT STATUS π«Ά
0on success π>0on error π
π AUTHORS π
See http://grid.ncsa.illinois.edu/myproxy/about for the list of MyProxy authors. the legends themselves, no cap π
π SEE ALSO π
myproxy-change-pass-phrase(1)myproxy-destroy(1)myproxy-info(1)myproxy-init(1)myproxy-logon(1)myproxy-retrieve(1)myproxy-store(1)myproxy-server.config(5)myproxy-admin-adduser(8)myproxy-admin-change-pass(8)myproxy-admin-query(8)myproxy-server(8)
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
- debian bookworm: myproxy-admin 6.2.14-2+b2 Β· NCSA
- debian trixie: myproxy-admin 6.2.16-4 Β· NCSA
- epel 10: myproxy-admin 6.2.20-1.el10_2 Β· NCSA AND BSD-4-Clause AND BSD-2-Clause AND Apache-2.0
- epel 9: myproxy-admin 6.2.20-1.el9 Β· NCSA AND BSD-4-Clause AND BSD-2-Clause AND Apache-2.0
- fedora 43: myproxy-admin 6.2.16-10.fc43 Β· NCSA AND BSD-4-Clause AND BSD-2-Clause AND Apache-2.0
- fedora 43: myproxy-admin 6.2.20-1.fc43 Β· NCSA AND BSD-4-Clause AND BSD-2-Clause AND Apache-2.0
- fedora 44: myproxy-admin 6.2.20-2.fc44 Β· NCSA AND BSD-4-Clause AND BSD-2-Clause AND Apache-2.0
- ubuntu jammy: myproxy-admin 6.2.9-2 Β· NCSA
- ubuntu noble: myproxy-admin 6.2.16-2build2 Β· NCSA
- ubuntu questing: myproxy-admin 6.2.16-4
- ubuntu resolute: myproxy-admin 6.2.20-1 Β· NCSA
- ubuntu stonking: myproxy-admin 6.2.20-2build1 Β· NCSA
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash on : a language model's rewrite of the original, under its terms