Skip to content

Fortified IDDocs

Databases

Configure PostgreSQL roles, schema migrations and backup for SDK Access Point message transport and evidence.

SDK Access Point uses PostgreSQL for outbound dispatch, inbound delivery and transport evidence. Prepare the database and service logins before installing the instance.

Property Purpose
database.url PostgreSQL JDBC URL. Set the deployment host, database, schema and TLS parameters. The external Docker example uses sslmode=verify-full and a mounted database CA.
database.user Login used by the runtime or migration invocation. Use a different login for each role.
database.password.env Name of the secret supplied to that process. The Docker delivery supplies the runtime and migration values from different files.

The migrator owns schema changes. The runtime login reads and writes the tables needed for dispatch and inbox processing, appends journal and signal evidence rows, and reads the migration history. Keep schema ownership, DDL and privileged database roles outside the runtime account. Database properties example

For the Docker delivery, run the explicit installer migration before starting the access point. For a standalone JAR invocation, run the selected release with --config <migration-properties> --migrate-only using the migration login. Start the application with AP_SKIP_DATABASE_MIGRATIONS=true and the restricted login after migration succeeds. Keep the instance configuration, credentials and database state separate from the release artifact. Installation

Include dispatch, inbox, transfer journal, signed evidence and schema history in the same backup and restore plan. The dispatch and inbox can hold package bytes. Restrict access to both the live database and backups accordingly. Restore into an isolated environment, inspect the schema history, check readiness and confirm that a pending package can still be retrieved. Recovery diagnostics · Logging and audit