Page History

...

• Vault URL: the base URL for which the Vault REST API is available.
• Vault Authentication Method Path: the path specifies the Vault Authentication Method to be used, see chapter Authentication Methods.
• Vault Truststore Path:  Should the Vault Server be configured for HTTPS connections then the indicated truststore has to include an X.509 certificate specified for the extended key usage of Server Authentication.
  • The truststore can include a self-signed certificate or a CA-signed certificate. Typically the Root CA certificate is used as otherwise the complete certificate chain involved in signing the Server Authentication certificate has to be available with the truststore.
  • If the Vault Server is operated for HTTPS connections and this setting is not specified then JOC Cockpit will use the truststore that is configured with the JETTY_BASE/resources/joc/joc.properties configuration file. This includes use of settings for the truststore password and truststore type.
• Vault Truststore Password: Should the Vault Server be configured for HTTPS connections and the indicated truststore be protected by a password then the password has to be specified.
• Vault Truststore Type: Should the Vault Server be configured for HTTPS connections then the type of the indicated truststore has to be specified being either PKCS12 or JKS (deprecated).
• Vault Application Token: The application token setting is available only if the VAULT-JOC-ACTIVE Identity Service Type is used.
  • JOC Cockpit requires this token in order to manage users with Vault, the token has to be created with Vault, see above chapter Application Role. This token allows JOC Cockpit to access the Vault REST API to manage user accounts.
  • This token is not used for login of users.  

...