Skip to main content
Skip table of contents

Set up MariaDB in Certificate Manager using Podman

This article is new for Certificate Manager 8.10.4.

This article describes how to install and set up the MariaDB database, used in Smart ID Certificate Manager (CM).

For detailed information about how to install MariaDB, see the documentation available at https://mariadb.org/ .

Prerequisites

  • Install the MariaDB database according to the instructions for the downloaded MariaDB installation package.

  • Extract the MariaDB database scripts create_db_and_role.sql, create_cmdb.sql, add_bootca.sql, located at certificate-manager-8.X.Y-Z.zip\cmdb-install-tool-8.X.Y.zip\install\MariaDB, from the server containerization zip file.

Step-by-step instruction

Edit settings on the MariaDB server

  1. Change the password for the lcmreq user, that will be created by the script below. The default password is REQreq01.

  2. Change the user host settings in the script to define which host address the user will access the database from. The default value is '%' which indicates that the user may use the database from any host.

  3. To enable interactive mode, login as superuser:

    CODE
    mysql --user=root --password
  4. Run the script, that creates the CMDB database, the lcmreq user and the cmdb_rw_role role, from the current interactive mode:

    CODE
    source create_db_and_role.sql >create_cmdb.log
  5. Check the log file.

  6. Run the script for creating the CMDB tables:

    CODE
    source create_cmdb.sql >create_cmdb.log
  7. Check the log file

  8. Run the script for adding the bootca: > source add_bootca.sql > add_bootca.log

  9. Check the log file.

Edit settings on the CM server

Navigate to the volume hosting the cm server config directory and update the database parameters in cm.conf

  • Database.name

  • Database.user

  • Database.password

Secure the connection

See Set up MariaDB in Certificate Manager.

 

JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.