Storing your repository in a database

In Visual Guard, the repository is the central location where all security data—such as users, roles, permissions, MFA settings, and audit logs—is stored and managed. Storing your repository in a database provides a secure, scalable, and reliable foundation for your application’s security infrastructure. By using a supported database engine like SQL Server or Oracle, organizations can ensure high performance, strong data integrity, and seamless integration with existing enterprise systems. This approach also simplifies backup, maintenance, and multi-environment deployments, making it the recommended method for managing Visual Guard repositories.

• For Oracle Database Installation:
  Visual Guard will create database objects in the schema associated to the specified user account (we recommend
  that you create a specific schema for Visual Guard repository). If your database
  DBA wants to create the database manually, you can find the database creation script
  in the directory <Visual Guard installation directory>\VisualGuardConsole\Database\Oracle. The DBA can use the script “Install.sql” and adapt it to create the database objects. It is necessary to modify the script to change the value <VISUAL_GUARD_SCHEMA>
  by the name of the schema that will contain Visual Guard database objects.
• For SQLServer database Installation:
  Visual Guard will create the database objects in the specified database. The default database name is “visualguarddb”. If The DBA of your database want to create manually the database, you can find the script of database creation in the directory <Visual Guard installation directory>\VisualGuardConsole\Database\SQLServer. The DBA can use the script “Install.sql” and adapt it to create the database objects.
  

  If the repository creation wizard does not detect the database, Visual Guard will create it.

How to grant access to the Visual Guard repository

• vg_BasicAccess: This role must be granted to a user account that will need to be authenticated by Visual Guard in your application.
• vg_UserAdminAccess: This role must be granted to a user account
  that will need to access the Visual Guard console as User Administrator. This role allows you to create or edit user accounts and to grant roles to this user.
• vg_DeveloperAccess: this role must be granted to a user account
  that will need to access the Visual Guard console as Developer. This role allows you to create or edit user accounts, roles, applications, permissions and permission sets.
• vg_FullAccess: this role must be granted to user account that will need to access the Visual Guard console as Master administrator. This role allows you to create or edit all Visual Guard entities and to drop the repository.