The globus-connect-server login command creates an authentication token on the local machine. Most globus-connect-server command commands require a token in order to manage or view the state of an Endpoint.
When you invoke this command, you must supply an argument that may
be either the endpoint ID (which is also the client id used to create the endpoint),
or the string
localhost string will only work if you are invoking
this command on a Data Transfer Node. The client id form of this command will
work on any machine with internet access.
When you run this command, it will print out a long URL that is a link
to the Globus Auth service. Follow that link, authenticate with your identity
provider, and then copy the
code value in the resulting web page into the terminal
where you are running this command. If successful, this command will print out a
message that you are successfully logged in.
You can now use the other globus-connect-server commands for which your Globus identity has been granted permissions. If your are the endpoint owner, you can create and manage storage gateways and mapped collections. If your endpoint is managed, you can also create other management roles.
Normally, the globus-connect-server login command obtains an OAuth refresh token, so that once you’ve logged in, you can perform many globus-connect-server commands without having to log in again. If you are done managing the endpoint and don’t require this behavior, you can use globus-connect-server logout to revoke the token.
- -h, --help
Show help message and exit.
Show the version and exit.
Do a fresh authentication flow, ignoring any existing credentials.