Skip to content

Fortified IDDocs

Installation

Prepare the host, install a signed SDK Access Point delivery and check that the private listener is ready.

Prepare release artifacts, instance configuration, TLS material and PostgreSQL access before starting the service. Keep configuration, keys, secrets and database state separate from the release directory.

The Docker delivery for a closed technical environment bundles the access point, Java runtime and SDK schemas in the supplied Linux image. The host needs Docker Engine, Docker Compose, Python 3 and OpenSSL. Use an external PostgreSQL database or select the synthetic database profile for an isolated test.

Installer operation Purpose
import Verify the signed delivery inventory and import its images into the local engine.
preflight Check the installation description, instance material and permissions.
migrate --authorize-migration Apply the schema using the separate migration login.
start Check migration state and the runtime login’s database privileges, then start the service.
stop Stop the access point in an orderly way while preserving data and configuration.
  1. Obtain the archive SHA-256, manifest SHA-256 and publisher public key through the trusted release channel. Check the archive hash before unpacking it or running the bundled tools.
  2. Prepare the instance using the examples from that archive. Choose host ports, participant IDs, certificates and database roles. Configuration · Key management and PKI
  3. Follow the delivery’s README.txt for the full arguments to import, run preflight, migrate and start. Follow the bounded error code if a step refuses to proceed.
  4. Use the supplied diagnostic identity and health client to check private readiness. Both listeners bind to IPv4 loopback in the closed Docker profile. Health checks

The Windows host-preparation tool provides a read-only host check. Run it in elevated 64-bit Windows PowerShell 5.1 from the installer engine directory:

Terminal window
.\windows-access-point.ps1 -Operation host-check -ExplainHostRefusal
$LASTEXITCODE

Exit code 0 means the check passed. Exit code 78 means the host was refused. The JSON report identifies the failed check with FailedCheck and ReasonCode. The host check does not install or authorize the service.

Send a synthetic package, inspect the signed transport receipt, and retrieve the package on the receiving side. Keep the original instance material and release identities available for operation and recovery. Integration · Recovery diagnostics

In this section