This page will describe 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 is most probably 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 how 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 avoid involuntary character replacement.
NOTE: In case you are using Ident type of authentication with PostgreSQL, run the psql commands as postgres user. Not as root .
Obtaining and installing PostgreSQL
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 vendor, so please follow their instructions to ensure the best possible configuration. We have tested Ubisecure CustomerID with PostgreSQL 9.6.10.
Configure PostgreSQL authentication
To allow SQL users to access PostgreSQL, we need to configure authentication methods in
Creating a database user
Use the following command to create a new user in the PostgreSQL database.
Creating the database
Below are example commands for creating a database for CustomerID usage. You should select suitable values for LC_COLLATE and LC_CTYPE based on your data needs. The values presented here are just examples to help you notice the settings.
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
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.