The installation process requires the password for a database administrator account that can create tables, views, and other artifacts in the databases. You can avoid using your database administrator account password by creating a temporary administrator for the installation process to use.
You would need a temporary database administrator account if the installer is creating the databases for you or if you manually create the databases and allow the installer to populate the databases for you. Use the appropriate steps for your database type to create a temporary database administrator.
The installation process requires the password for an administrator account in Oracle that can create tables, views, and other artifacts in the databases. You can avoid specifying the password for the Oracle system account by creating a temporary administrator for the installation process to use.
IMPORTANT:If you create the Oracle database administrator in a database hosted in the cloud, ensure that you follow the documentation for the cloud platform you are using to have the proper rights for the database administrator. The following steps are for databases installed on premise and might not be correct if you are installing in the cloud.
The temporary account must have the CONNECT role and the following system privileges:
Alter user
Create public synonym
Create user
Drop public synonym
Drop user
Grant any object privilege
Grant any privilege
Grant any role
During installation, you can also select Generate SQL for later, which prevents the installation program from creating the tables, views, and artifacts in the Identity Governance or Identity Reporting database. Instead, the program generates a SQL file for each schema, which your database administrator can run to update the database. For more information about using the SQL files, see Section 5.11, Configuring the Databases Using the SQL Scripts.
The installation process requires the password for an administrator account in Microsoft SQL Server that can create databases, tables, views, and other artifacts in the databases. You can avoid specifying the password for the admin account by creating a temporary administrator for the installation process to use.
IMPORTANT:If you create the Microsoft SQL database administrator in a database hosted in the cloud, ensure that you follow the documentation for the cloud platform you are using to have the proper rights for the database administrator. The following steps are for databases installed on premise and might not be correct if you are installing in the cloud.
The temporary account must have the following properties:
Create any database
Alter any login
Alter any user
Create role
During installation, you can also select Generate SQL for later, which prevents the installation program from creating the tables, views, and artifacts in the Identity Governance or Identity Reporting databases. Instead, the program generates a SQL file for each database, which your database administrator can run to update the database. For more information about using the SQL files, see Configuring the Databases Using the SQL Scripts.
The installation process requires the password for an administrator account in PostgreSQL that can create databases, roles, tables, views, and other artifacts in the databases. You can avoid specifying the password for the postgres account by creating a temporary administrator for the installation process to use.
IMPORTANT:If you create the PostgreSQL database administrator in a database hosted in the cloud, ensure that you follow the documentation for the cloud platform you are using to have the proper rights for the database administrator. The following steps are for databases installed on premise and might not be correct if you are installing in the cloud.
The temporary account must have the following properties:
LOGIN
SUPERUSER
CREATEDB
CREATEROLE
The temporary account must have privileges to complete the following tasks:
create databases
create roles
assign ownership of each database to a role so that this role can then create tables, views, and other artifacts within the databases that it owns
grant connect on a database to a role
grant one role to another.
During installation, you can also select Generate SQL for later, which prevents the installation program from creating the tables, views, and artifacts in the Identity Governance or Identity Reporting databases. Instead, the program generates a SQL file for each database, which your database administrator can run to update each database. For more information about using the SQL files, see Section 5.11, Configuring the Databases Using the SQL Scripts.