GLOBUS GET-IDENTITIES
DESCRIPTION
Lookup Globus Auth Identities given one or more uuids and/or usernames.
Default output resolves each UUID to a username and each username to a UUID, with one output per line in the same order as the inputs. If a particular input had no corresponding identity in Globus Auth, "NO_SUCH_IDENTITY" is printed instead.
If more fields are desired, --verbose will give tabular output, but does not guarantee order and ignores inputs with no corresponding Globus Auth identity.
OPTIONS
- -v, --verbose
-
Control level of output
- -h, --help
-
Show this message and exit.
-
-F, --format
[unix|json|text] -
Output format for stdout. Defaults to text
-
--jmespath, --jq
TEXT -
A JMESPath expression to apply to json output. Takes precedence over any specified '--format' and forces the format to be json processed by this expression
-
--map-http-status
TEXT -
Map HTTP statuses to any of these exit codes: 0,1,50-99. e.g. "404=50,403=51"
EXAMPLES
Resolve a user ID (outputs the user’s username)
$ globus get-identities c699d42e-d274-11e5-bf75-1fc5bf53bb24Resolve a username (outputs the user’s ID)
$ globus get-identities go@globusid.orgResolve multiple usernames and or IDs with tabular output
$ globus get-identities --verbose go@globusid.org clitester1a@globusid.org 84942ca8-17c4-4080-9036-2f58e0093869EXIT STATUS
0 on success.
1 if a network or server error occurred, unless --map-http-status has been used to change exit behavior on http error codes.
2 if the command was used improperly.
3 if the command was used on the wrong type of object, e.g. a collection command used on an endpoint.
4 if the command has authentication or authorization requirements which were not met, as in ConsentRequired errors or missing logins.