Skip to content

Latest commit

 

History

History
82 lines (72 loc) · 4.56 KB

README.md

File metadata and controls

82 lines (72 loc) · 4.56 KB

back to Commands

om configure-authentication

The configure-authentication command will allow you to setup your user account on the Ops Manager with the internal userstore mechanism.

To set up your Ops Manager with SAML authentication instead, use configure-saml-authentication.

Command Usage

Usage:
  om [OPTIONS] configure-authentication [configure-authentication-OPTIONS]

This unauthenticated command helps setup the internal userstore authentication
mechanism for your Ops Manager.

Application Options:
      --ca-cert=                      OpsManager CA certificate path or value
                                      [$OM_CA_CERT]
  -c, --client-id=                    Client ID for the Ops Manager VM (not
                                      required for unauthenticated commands)
                                      [$OM_CLIENT_ID]
  -s, --client-secret=                Client Secret for the Ops Manager VM (not
                                      required for unauthenticated commands)
                                      [$OM_CLIENT_SECRET]
  -o, --connect-timeout=              timeout in seconds to make TCP
                                      connections (default: 10)
                                      [$OM_CONNECT_TIMEOUT]
  -d, --decryption-passphrase=        Passphrase to decrypt the installation if
                                      the Ops Manager VM has been rebooted
                                      (optional for most commands)
                                      [$OM_DECRYPTION_PASSPHRASE]
  -e, --env=                          env file with login credentials
  -p, --password=                     admin password for the Ops Manager VM
                                      (not required for unauthenticated
                                      commands) [$OM_PASSWORD]
  -r, --request-timeout=              timeout in seconds for HTTP requests to
                                      Ops Manager (default: 1800)
                                      [$OM_REQUEST_TIMEOUT]
  -k, --skip-ssl-validation           skip ssl certificate validation during
                                      http requests [$OM_SKIP_SSL_VALIDATION]
  -t, --target=                       location of the Ops Manager VM
                                      [$OM_TARGET]
      --trace                         prints HTTP requests and response
                                      payloads [$OM_TRACE]
  -u, --username=                     admin username for the Ops Manager VM
                                      (not required for unauthenticated
                                      commands) [$OM_USERNAME]
      --vars-env=                     load vars from environment variables by
                                      specifying a prefix (e.g.: 'MY' to load
                                      MY_var=value) [$OM_VARS_ENV]
  -v, --version                       prints the om release version

Help Options:
  -h, --help                          Show this help message

[configure-authentication command options]
      -u, --username=                 admin username [$OM_USERNAME]
      -p, --password=                 admin password [$OM_PASSWORD]
      -d, --decryption-passphrase=    passphrase used to encrypt the
                                      installation [$OM_DECRYPTION_PASSPHRASE]
          --http-proxy-url=           proxy for outbound HTTP network traffic
          --https-proxy-url=          proxy for outbound HTTPS network traffic
          --no-proxy=                 comma-separated list of hosts that do not
                                      go through the proxy
          --precreated-client-secret= create a UAA client on the Ops Manager
                                      vm. The client_secret will be the value
                                      provided to this option

    config file interpolation:
      -c, --config=                   path to yml file for configuration (keys
                                      must match the following command line
                                      flags)
          --vars-env=                 load variables from environment variables
                                      matching the provided prefix (e.g.: 'MY'
                                      to load MY_var=value) [$OM_VARS_ENV]
      -l, --vars-file=                load variables from a YAML file
      -v, --var=                      load variable from the command line.
                                      Format: VAR=VAL