Setting up a nevisMeta Instance

Preconditions

• nevisMeta must be installed on the relevant target hosts.
  • The minimum required version is: 1.5.1.6
  • Use the nevisAppliance extended image or check the nevisMeta documentation on how to install nevisMeta.
• nevisMeta requires a MariaDB database.
  • You can use the nevisAppliance DB image.
  • Check the nevisMeta documentation on how to set up the database.
• You need a Realm pattern to provide the authentication flow and to protect the nevisMeta Web Console.
  • To access the nevisMeta Web Console, the authenticated user must have the role nevisMeta.admin.

Realm Patterns

nevisAdmin 4 provides provides several Realm patterns. You can use any Realm pattern for this purpose. The Authentication Realmis the most high-level and convenient pattern.

Quick Start

Perform the following steps to set up a nevisMeta instance:

1. Add a nevisMeta Instance pattern. Configure the pattern as follows:

   1. Enter a deployment target in the Deployment Target field.
      1. Use a group, host, or service that exists in your inventory.
      2. The target hosts must have nevisMeta installed (version >= 1.5.1.6).
   2. Add a nevisMeta Database Connector pattern in the Database Connector field.

2. Configure the nevisMeta Database Connector pattern as follows:

   1. Enter a relevant URL in the Connection URL field. For example: "jdbc:mariadb://nevisdb:3306/nevismeta".
   2. Enter the name of the DB schema owner in the Username field. For example: "umet01".
   3. Connect a variable to the Password field.
      1. Set the value for this variable in your inventory.

3. Add a nevisMeta Web Console pattern. Configure the pattern as follows:

   1. Assign the previously configured nevisMeta Instance pattern to the nevisMeta field.
   2. Assign a Virtual Host pattern to the Virtual Host field. The nevisMeta Web Console is accessible on this virtual host via the path /nevismeta/.
   3. Assign an Authentication Realm pattern to the Authentication Realm field.
   4. Assign a Nevis SecToken pattern to the Application Access Token field.
      1. The pattern verifies that this Nevis SecToken pattern is also assigned to the Realm pattern that you configured as a precondition (see the section Preconditions).

The following figure shows the nevisMeta patterns in an example configuration:

This example uses automatic key management.

For production setups, use the PEM- or nevisKeybox Store patterns instead.