myproxy-store(1)
π myproxy-store(1) β bestie, we're uploading a credential π
MyProxy Β· section 1 Β· the one where you stash your end-entity credential so you can grab it later π
β¨ NAME β¨
myproxy-store β store end-entity credential for later retrieval π«Ά
πΈ SYNOPSIS πΈ
myproxy-store [ options ]
π¦ DESCRIPTION π¦
okay so. myproxy-store uploads a credential to a myproxy-server(8) so you (or, like, future you) can retrieve it later. πΎβ¨
The tea is: you must already have a valid proxy credential when you run this β one that was generated by grid-proxy-init or grabbed via myproxy-logon(1). No proxy, no store, periodt.
Now, the spicy difference: unlike myproxy-init(1), this command transfers the private key over the network (over a private channel). π³ Yeah. The key moves. It's over a private channel, so breathe, but still β that's the whole thing that makes this command different.
In the default mode, it takes the credentials hanging out in ~/.globus/usercert.pem and ~/.globus/userkey.pem and stores them in the myproxy-server(8) repository. Then proxy credentials with a default lifetime of 12 hours can be retrieved by myproxy-logon(1) using the credential passphrase. π
You can override all that default behavior with the options below. The default behavior is literally just the starting point, bestie.
β οΈ Important: the hostname where themyproxy-server(8)is running must be specified β either by defining theMYPROXY_SERVERenvironment variable or by using the-soption. One of those two. That's the vibe check you cannot skip. π¨
β¨ OPTIONS β¨
-h,--helpβ shows you the command usage text and then exits. bye π-u,--usageβ also shows you the command usage text and exits. (yes, it's basically the same energy as-h, we don't question it) π-v,--verboseβ turns on verbose debugging output to the terminal. for when you need to see everything π-V,--versionβ prints version information and exits. π-s hostname[:port],--pshost hostname[:port]β specifies the hostname(s) of themyproxy-server(s). You can list multiple hostnames in a comma-separated list, and each hostname can optionally be followed by a':'and a port number. This option is required if theMYPROXY_SERVERenvironment variable isn't defined. If you do specify it, it overrides theMYPROXY_SERVERenvironment variable. And if you tack a port number onto a hostname, that port overrides the-poption and theMYPROXY_SERVER_PORTenvironment variable for that host. π-p port,--psport portβ specifies the TCP port number of themyproxy-server(8). Default:7512. If you specify it, it overrides theMYPROXY_SERVER_PORTenvironment variable.-l username,--username usernameβ specifies the MyProxy account that the credential should be stored under. By default the command uses whatever's in theLOGNAMEenvironment variable. Use this to pick a different account username on the MyProxy server. and ngl, the MyProxy username does not have to correspond to a real Unix username β it's its own thing. πͺͺ-c filename,--certfile filenameβ specifies the filename of the source certificate. π-y filename,--keyfile filenameβ specifies the filename of the source private key. π-t hours,--proxy_lifetime hoursβ 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 default username instead of theLOGNAMEenvironment variable. main character DN energy π-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: themyproxy-server.config(5)server-wide policy must also allow"anonymous"clients for this option to actually do anything. both doors, bestie.-A,--allow_anonymous_renewersβ allow credentials to be renewed by any client. Any client with a valid credential whose subject name 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's included only for the sake of completeness. it's giving "we put it here so the set is complete, not because you should use it" π-r name,--retrievable_by nameβ allow the specified entity to retrieve credentials. See the-xand-Xoptions for controlling name matching behavior.-E name,--retrieve_key nameβ allow the specified entity to retrieve end-entity credentials. See the-xand-Xoptions for controlling name matching behavior.-R name,--renewable_by nameβ allow the specified entity to renew credentials. See the-xand-Xoptions for controlling name matching behavior.-Z name,--retrievable_by_cert nameβ allow the specified entity to retrieve credentials without a passphrase. See the-xand-Xoptions for controlling name matching behavior.-x,--regex_dn_matchβ says that the names used with the following options β-r,-E,-R, and-Zβ will be matched against the full certificate subject distinguished name (DN) according to REGULAR EXPRESSIONS inmyproxy-server.config(5). π§-X,--match_cn_onlyβ says that the names used with the following options β-r,-E,-R, and-Zβ will be matched against the certificate subject common name (CN) according to REGULAR EXPRESSIONS inmyproxy-server.config(5). For example, if you pass an argument of-r "Jim Basney", then the resulting policy will be"*/CN=Jim Basney". This is the default behavior. β¨-k name,--credname nameβ specifies the credential name. π·οΈ-K description,--creddesc descriptionβ specifies the credential description. π
π EXIT STATUS π
0 on success, >0 on error. that's it, that's the whole mood.
π FILES π
~/.globus/usercert.pemβ the default location of the certificate to be stored on themyproxy-server. Use the--certfileoption to override it.~/.globus/userkey.pemβ the default location of the private key to be stored on themyproxy-server. Use the--keyfileoption to override it.-T,--trustrootsβ retrieve the CA certificates directory from the server (if available) and store it in the location specified by theX509_CERT_DIRenvironment variable if it's set, or/etc/grid-security/certificatesif running as root, or~/.globus/certificatesif running as non-root.
π okay bestie, real talk: in the original manual this -T, --trustroots entry is genuinely sitting down here in the FILES section instead of up in OPTIONS. That's just how it is. I'm not moving it, I'm not hiding it, we're keeping the chaos exactly where it lives. π
π ENVIRONMENT π
GLOBUS_GSSAPI_NAME_COMPATIBILITYβ by default, this client performs a reverse-DNS lookup to determine the FQHN (Fully Qualified Host Name) to use when verifying the identity of the server, by checking the FQHN against the CN in the server's certificate. Setting this variable toSTRICT_RFC2818will cause the reverse-DNS lookup to NOT be performed, and the user-specified name to be used instead. β οΈ This variable setting is ignored ifMYPROXY_SERVER_DN(described later) is set.MYPROXY_SERVERβ specifies the hostname(s) where themyproxy-server(8)is running. You can list multiple hostnames in a comma-separated list, each hostname optionally followed by a':'and port number. This environment variable can be used in place of the-soption. πMYPROXY_SERVER_PORTβ specifies the port where themyproxy-server(8)is running. This environment variable can be used in place of the-poption.MYPROXY_SERVER_DNβ specifies the distinguished name (DN) of themyproxy-server(8). All MyProxy client programs authenticate the server's identity. By default, MyProxy servers run with host credentials, so the MyProxy client programs expect the server to have a distinguished name with"/CN=host/<fqhn>"or"/CN=myproxy/<fqhn>"or"/CN=<fqhn>"(where<fqhn>is the fully-qualified hostname of the server). If the server is running with some other DN, you can set this environment variable to tell the MyProxy clients to accept the alternative DN. Also seeGLOBUS_GSSAPI_NAME_COMPATIBILITYabove. πMYPROXY_TCP_PORT_RANGEβ specifies a range of valid port numbers in the form"min,max"for the client side of the network connection to the server. By default, the client binds to any available port. Use this environment variable to restrict the ports used to a range allowed by your firewall. π§± If unset, MyProxy will follow the setting of theGLOBUS_TCP_PORT_RANGEenvironment variable.X509_USER_CERTβ specifies a non-standard location for the certificate to be used for authentication to themyproxy-server(8). It also specifies the location for the certificate to be stored, unless the-coption is given. two jobs, one variable πX509_USER_KEYβ specifies a non-standard location for the private key to be used for authentication to themyproxy-server(8). It also specifies the location for the private key to be stored, unless the-yoption is given.X509_USER_PROXYβ specifies a non-standard location for the proxy credential to be used for authentication to themyproxy-server(8).X509_CERT_DIRβ specifies a non-standard location for the CA certificates directory. π
π AUTHORS π
See http://grid.ncsa.illinois.edu/myproxy/about for the list of MyProxy authors. π«Ά
πΈ SEE ALSO πΈ
myproxy-change-pass-phrase(1), myproxy-destroy(1), myproxy-get-trustroots(1), myproxy-info(1), myproxy-logon(1), myproxy-retrieve(1), myproxy-server.config(5), myproxy-admin-adduser(8), myproxy-admin-change-pass(8), myproxy-admin-load-credential(8), myproxy-admin-query(8), myproxy-server(8) myproxy-retrieve(1)
okay that's the whole page, bestie, you ate it πβ¨ this was MyProxy, dated 2011-09-05, and that's the whole sign-off β go store that credential, you gorgeous thing ππ¦π
π¦ where this page comes from
- debian bookworm: myproxy 6.2.14-2+b2 Β· NCSA
- debian trixie: myproxy 6.2.16-4 Β· NCSA
- epel 10: myproxy 6.2.20-1.el10_2 Β· NCSA AND BSD-4-Clause AND BSD-2-Clause AND Apache-2.0
- epel 9: myproxy 6.2.20-1.el9 Β· NCSA AND BSD-4-Clause AND BSD-2-Clause AND Apache-2.0
- fedora 43: myproxy 6.2.16-10.fc43 Β· NCSA AND BSD-4-Clause AND BSD-2-Clause AND Apache-2.0
- fedora 43: myproxy 6.2.20-1.fc43 Β· NCSA AND BSD-4-Clause AND BSD-2-Clause AND Apache-2.0
- fedora 44: myproxy 6.2.20-2.fc44 Β· NCSA AND BSD-4-Clause AND BSD-2-Clause AND Apache-2.0
- ubuntu jammy: myproxy 6.2.9-2 Β· NCSA
- ubuntu noble: myproxy 6.2.16-2build2 Β· NCSA
- ubuntu questing: myproxy 6.2.16-4
- ubuntu resolute: myproxy 6.2.20-1 Β· NCSA
- ubuntu stonking: myproxy 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