This page describes how to install a very basic PostgreSQL Server RDBMS installation with a basic database for Ubisecure CustomerID. Many details will vary on a per customer basis, so further tuning is left to the integrator. One significant detail is to manage the collation rules on a per-column basis, therefore it may be necessary to make changes to the provided Database Definition Language (DDL) files before they are used to create the database tables for Ubisecure CustomerID. Collations define how text is compared and sorted and whether searches should behave in a case sensitive or insensitive manner.
Following commands are just examples of how to install a basic PostgreSQL database. You might want to use your own commands. Don't copy and paste the commands in this chapter. Write them by hand to the command prompt to avoid involuntary character replacement.
Obtaining and Installing PostgreSQL
Ubisecure CustomerID requires a PostgreSQL database which is not included in the distribution.
Ubisecure CustomerID is tested with PostgreSQL 9.6.10.
PostgreSQL binaries and instructions on how to use platform specific package managers to download and install PostgreSQL, can be found at the following URL:
Having obtained PostgreSQL binaries, run the wizard or relevant binaries to install. The installation process is documented and maintained by your PostgreSQL provider, so please follow their instructions to ensure the best possible configuration.
The basic steps are listed here PostgreSQL Windows installation - CustomerID.
Creating a Database User
Use the following command to create a new user in the PostgreSQL database.
When prompted, enter the password given in the installer wizard window during the PostgreSQL installation process.
Creating the Database
Below are example commands for creating a database for CustomerID usage. By default collation settings will be based on the locale settings of the Windows installation.
Applying the CustomerID DDL to PostgreSQL
When the database structure has been created, run the cid_init.sql and create the relevant views for SSO Server
When prompted, enter the password from the
database.password value of the
If you notice something wrong with the database at this point, it is possible to drop the tables using the script cid-drop.sql. After this, the DDL can be modified and imported again. Note that all inserted data in the database will be lost when the tables are dropped.