cec config add
Configure a new connection to a running server and persist credentials locally
Synopsis
DESCRIPTION
Launch an interactive process to configure a connection to a running Cells server. By default, we use a secure OAuth2 process based on 'Authorization Code' Grant.
If necessary, you might use an alternative authorization process and/or execute this process non-interactively calling one of the defined sub-commands.
Once a connection with the server is established, it stores necessary information locally, keeping the sensitive bits encrypted in the client machine keyring. If you want to forget a connection, the config file and keyring can be cleant out by calling the 'config rm' subcommand.
WARNING
If no keyring is defined in the client machine, all information is stored in clear text in a config file of the working directory.
./cec config add [flags]
Options
-h, --help help for add
Options inherited from parent commands
--config string Location of Cells Client's config files (default: /home/teamcity/.config/pydio/cells-client/config.json)
--log string change log level (default: info) (default "info")
--login string The user login, for Client auth only
--no-cache Force token refresh at each call. This might slow down scripts with many calls
--password string The user password, for Client auth only
--skip-keyring Explicitly tell the tool to *NOT* try to use a keyring, even if present. Warning: sensitive information will be stored in clear text
--skip-verify By default the Cells Client verifies the validity of TLS certificates for each communication. This option skips TLS certificate verification
-t, --token string A valid Personal Access Token (PAT)
-u, --url string The full URL of the target server
SEE ALSO
- ./cec config - Manage authentication profiles
- ./cec config add client-auth - Connect to the server using Client Credentials
- ./cec config add oauth - Use OAuth2 credential flow to login to the server
- ./cec config add token - Configure Authentication using a Personal Access Token