External Database Connection Strings

Privileged Access Manager supports a wide range of the most popularly used databases system in the market.

When configuring PAM to use your own database, you will need to supply the database connection string.

In general, the connection string will comply with the following example:

db-host or db-host:port

NOTE: The installation process does not create its own database or tablespace but rather makes use of an existing one. With that in mind, please ensure one with the name “PamDB” already exists as this will be used by the application.

Apache Derby

db-host or db-host:port

Microsoft SQL Server

db-host or db-host:port


db-host or db-host:port


Service: //db-host/db-service

Instance: //db-host:port:SID


db-host or db-host:port

PostgreSQL database account management

PAM users get manage accounts in PostgreSQL database including Check Status and Password Reset tasks including direct and shadow account access as well as permission and workflow based password unlock and custom script execution.

Initially hidden record type for PostgreSQL database including check status and password reset tasks based on the PostgreSQL Connection string given by

host:port/database, host/database, host[:port]/database

or full JDBC connection string:


To enable account management:

  • Connection (Type: String, Display Name: Connection String) to define host:port/database connection string
  • CommandUser (Type: String, Display Name: Command User) to define account login
  • CommandPassword (Type: String, Display Name: Command Password) to define account password

If you want to change the database after deployment, please see the following article for more information: Changing PAM’s back-end Database