Skip to main content

​
Requirements

​
Networking

Certain ports must be accessible to connect to Formal Resources. You can listen on multiple ports simultaneously for various Resources. For accessing Postgres, you may assign any port except 8080 (Connector’s health check port). Ensure your security groups are configured to allow traffic on the designated port.

​
Database Health Check

Formal periodically assesses the health of the database. Specify the database to use for the health check by entering its name. If no database health check is configured (see Database Health Check Configuration), the system will default to using the postgres database.

​
Connect to Postgres

​
PSQL

To connect using psql, execute the following command: 
psql -h CONNECTOR_HOSTNAME -p PORT -d DATABASE_NAME -U FORMAL_USERNAME
Make sure to replace CONNECTOR_HOSTNAME, PORT, DATABASE_NAME, and FORMAL_USERNAME with the right values. To learn more about users, check out Native Users.
You can access your Formal Credentials in the Formal console.
You are free to use any preferred client.

​
Smart Routing

The Connector features Smart Routing for PostgreSQL, allowing the linkage of an unlimited number of Resources over the same port (e.g. 5432). There are two methods to specify the resource you wish to connect to:
  1. Specify it in the JDBC params via the following option: options=formal_resource_name=[name of the datastore]
  2. Provide the name of the resource following the database name:
psql -h CONNECTOR_HOSTNAME -p 5432 -d DATABASE_NAME@RESOURCE_NAME -U idp:formal:human:[email protected]
It is possible to attach multiple hostnames to a single resource. To specify the hostname of the resource you wish to connect to, you can use the following format: 
psql -h CONNECTOR_HOSTNAME -p 5432 -d DATABASE_NAME@RESOURCE_NAME@RESOURCE_HOSTNAME_NAME -U idp:formal:human:[email protected]
Replace CONNECTOR_HOSTNAME, DATABASE_NAME, RESOURCE_NAME, and RESOURCE_HOSTNAME_NAME with the right values.

​
Policy Evaluation

Formal supports the following policy evaluation stages for Postgres:
  • Session: Evaluate and enforce policies at connection time
  • Pre-Request: Evaluate and enforce policies before query execution
  • Post-Request: Evaluate and enforce policies after data retrieval