...
Only Local User Account authentication is supported for the CLI.
SSO and LDAP authentication is only used for the Graphical User Interface.See Waarp Gateway Client Connection Settings on how to give the credentials
The authentication options are:
-a <ADDRESS>, --address=<ADDRESS>
The address of the gateway instance to query. If the parameter is absent, the address will be retrieved from the environment variable UDMG_SERVER_ADDRESS(see below).
This address must be provided as a DSN (Data Source Name):
[http|https]://<login>:<password>@<host>:<port>`
The protocol can be http or https depending on the configuration of the REST interface of the gateway.
The required login and password are the identifiers of a user. The user and password can be omitted, in which case they will be requested via a terminal prompt.
-i, --insecure
Disables certificate validation of the Gateway service REST interface. Can be used for self-signed certificates and testing.
| Note | ||
|---|---|---|
| ||
The connection settings are already configured on the UDMG terminal environment.Since server certificate validation is no longer done, the client blindly trusts the server. This can be a security hole if you are not absolutely sure of the server when using this option. |
UDMG_SERVER_ADDRESS
If the Gateway address is not provided in the command via the -a option , the address will be retrieved from this environment variable. The syntax of the address remains identical to that described above.
UDMG_SERVER_INSECURED
Disables certificate validation of the Gateway service REST interface. (equivalent to option -i)
PGP Key Management
PGP key records can be stored in the UDMG database and retrieved with the CLI or the REST API to be used by scripts or by Universal Controller tasks without having to keep them in a local keyring.
...