myproxy-logon(1)

💖 myproxy-logon — retrieve a credential 💖

okay bestie, so you know how I'm always going on about myproxy-logon(1)? yeah. that's this. it's a MyProxy thing. let's get into it ✨

🌸 NAME 🌸

myproxy-logon — retrieve a credential. that's it, that's the whole job. she fetches. she serves. 💅

🦋 SYNOPSIS 🦋

myproxy-logon [ options ]

myproxy-get-delegation [ options ]

✨ DESCRIPTION ✨

so the myproxy-logon command retrieves a proxy credential from the myproxy-server(8) — and that credential has to have been previously stored using myproxy-init(1) or myproxy-store(1), okay? like, she's not gonna manifest it out of thin air, someone had to put it there first. 💜

she can also be used to retrieve short-lived end entity credentials from a myproxy-server(8) that's configured to act as a Certificate Authority. yes queen, CA energy. 👑

in the default mode, the command prompts for the MyProxy pass phrase associated with the credential to be retrieved, and then stores the retrieved credential in the location specified by the X509_USER_PROXY environment variable — or in /tmp/x509up_u<uid> if that environment variable is not set. remember that path. it lives in your head rent free now. 🌈

also!! the myproxy-logon command is also available under the name myproxy-get-delegation for backward compatibility. two names, one icon. 🎀

💅 OPTIONS 💅

• -h, --help — displays command usage text and exits. your girl is helpful.
• -u, --usage — displays command usage text and exits. yeah, same energy as -h, she contains multitudes.
• -v, --verbose — enables verbose debugging output to the terminal. all the tea, spilled. 🔥
• -V, --version — displays version information and exits.
• -s hostname[:port], --pshost hostname[:port] — specifies the hostname(s) of the myproxy-server(s). multiple hostnames, each hostname optionally followed by a : and port number, may be specified in a comma-separated list. this option is required if the MYPROXY_SERVER environment variable is not defined. if specified, this option overrides the MYPROXY_SERVER environment variable. and if a port number is specified with a hostname, it will override the -p option as well as the MYPROXY_SERVER_PORT environment variable for that host. so many overrides, so little time. 😭
• -p port, --psport port — specifies the TCP port number of the myproxy-server(8). default: 7512. ✨
• -l username, --username username — specifies the MyProxy account under which the credential to retrieve is 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. the MyProxy username need not correspond to a real Unix username. she's fake but she's valid. 💖
• -d, --dn_as_username — use the certificate subject (DN) as the default username, instead of the LOGNAME environment variable. when used with the -a option, the certificate subject of the authorization credential is used. otherwise, the certificate subject of the default credential is used.
• -t hours, --proxy_lifetime hours — specifies the lifetime of credentials retrieved from the myproxy-server(8) using the stored credential. the resulting lifetime is the shorter of the requested lifetime and the lifetime specified when the credential was stored using myproxy-init(1). default: 12 hours. so like, you can ask for a lot, but you get what you get. lowkey humbling. 🙈
• -o file, --out file — specifies where the retrieved proxy credential should be stored. if this option is not specified, the proxy credential will be stored in the location specified by the X509_USER_PROXY environment variable or /tmp/x509up_u<uid> if that environment variable is not set. to write the credential to the command's standard output rather than to a file, use -o -. yes, dash. she's the main character. 🌟
• -a file, --authorization file — use this option to specify an existing, valid credential that you want to renew. renewing a credential generally requires two certificate-based authentications. the client authenticates with its identity, using the credential in the standard location or specified by the X509_USER_PROXY or X509_USER_CERT and X509_USER_KEY environment variables, in addition to authenticating with the existing credential, in the location specified by this option, that it wants to renew. two-factor but make it grid. 🔐
• -k name, --credname name — specifies the name of the credential that is to be retrieved or renewed.
• -S, --stdin_pass — by default, the command prompts for a passphrase and reads the passphrase from the active tty. when running the command non-interactively, there may be no associated tty. specifying this option tells the command to read passphrases from standard input without prompts or confirmation. for the script girlies. 🫶
• -n, --no_passphrase — don't prompt for a credential passphrase. use other methods for authentication, such as Kerberos ticket or X.509 certificate. this option is implied by -a since passphrase authentication is not used for credential renewal.
• -T, --trustroots — retrieve CA certificates directory from server (if available) to store in the location specified by the X509_CERT_DIR environment variable if set, or /etc/grid-security/certificates if running as root, or ~/.globus/certificates if running as non-root. trust tree. 🌳
• -b, --bootstrap — unless this option is specified, then if the X509_CERT_DIR exists and the CA that signed the myproxy-server(8) certificate is not trusted, myproxy-logon will fail with an error, to protect against man-in-the-middle attacks. if, however, this option is specified, myproxy-logon will accept the CA to bootstrap trust. this option implies -T. okay so this one is the spicy one, bestie — read it twice. 👀
• -q, --quiet — only write output messages on error. silent but deadly (to bugs).
• -N, --no_credentials — authenticate only. don't retrieve credentials. sometimes you just wanna say hi. 👋
• -m voms, --voms voms — add VOMS attributes to the credential by running voms-proxy-init on the client-side after retrieving the credential from the myproxy-server(8). the VOMS VO name must be provided, as required by voms-proxy-init -voms. the voms-proxy-init command must also be installed and configured to use this option. for example, the VOMS_USERCONF environment variable may need to be set for voms-proxy-init to run correctly. attribute glow-up. ✨
• -Q file, --certreq file — specify the path to a PEM formatted certificate request to use when requesting a certificate from the myproxy-server(8), rather than allowing myproxy-logon to generate the private key and certificate request itself. in this case, myproxy-logon will not output a private key but will only output the signed certificate and (as needed) certificate chain. to read the certificate request from standard input rather than from a file, use -Q -. bring your own CSR, she respects it. 💅

🔥 EXIT STATUS 🔥

0 on success, >0 on error. zero means slay, anything else means we're in our flop era. 😭

🌈 ENVIRONMENT 🌈

• GLOBUS_GSSAPI_NAME_COMPATIBILITY — this client will, by default, perform a reverse-DNS lookup to determine the FQHN (Fully Qualified Host Name) to use in verifying the identity of the server by checking the FQHN against the CN in server's certificate. setting this variable to STRICT_RFC2818 will cause the reverse-DNS lookup to NOT be performed and the user-specified name to be used instead. this variable setting will be ignored if MYPROXY_SERVER_DN (described later) is set. iykyk. 👑
• MYPROXY_SERVER — specifies the hostname(s) where the myproxy-server(8) is running. multiple hostnames can be specified in a comma separated list with each hostname optionally followed by a : and port number. this environment variable can be used in place of the -s option.
• MYPROXY_SERVER_PORT — specifies the port where the myproxy-server(8) is running. this environment variable can be used in place of the -p option.
• MYPROXY_SERVER_DN — specifies the distinguished name (DN) of the myproxy-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 see GLOBUS_GSSAPI_NAME_COMPATIBILITY above. 👀
• 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 will bind 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 the GLOBUS_TCP_PORT_RANGE environment variable. firewall-approved only, periodt. 🚧
• X509_USER_CERT — specifies a non-standard location for the certificate to be used for authentication to the myproxy-server(8).
• X509_USER_KEY — specifies a non-standard location for the private key to be used for authentication to the myproxy-server(8).
• X509_USER_PROXY — specifies a non-standard location for the proxy credential to be used for authentication to the myproxy-server(8). also specifies the output location for the proxy credential to be retrieved from the myproxy-server(8) unless the -o option is given. she does double duty, she's booked and busy. 💅
• X509_CERT_DIR — specifies a non-standard location for the CA certificates directory.
• MYPROXY_KEYBITS — specifies the size for RSA keys generated by MyProxy. by default, MyProxy generates 2048 bit RSA keys. set this environment variable to 1024 for 1024 bit RSA keys. big key energy only, bestie. 🔑

🧚 AUTHORS 🧚

see http://grid.ncsa.illinois.edu/myproxy/about for the list of MyProxy authors. the whole squad, credited. 🫶

🍓 SEE ALSO 🍓

myproxy-change-pass-phrase(1), myproxy-destroy(1), myproxy-get-trustroots(1), myproxy-info(1), myproxy-init(1), myproxy-retrieve(1), myproxy-server.config(5), myproxy-store(1), myproxy-admin-adduser(8), myproxy-admin-change-pass(8), myproxy-admin-load-credential(8), myproxy-admin-query(8), myproxy-server(8)

and that's the whole page, bestie. MyProxy, dated 2010-09-09 — yes she's been iconic since 2010 and she's still serving. mwah. 💖