Handle a macOS executable verification warning ​

A macOS warning about an unverified developer is a host security decision made before Coordinator DB processes SQL. Confirm where the executable came from and whether it is the file you intended to run before changing that decision.

Verify the intended artifact ​

Use the project's documented installation path or an artifact approved by your organization. Check any available signature or checksum against the trusted source through a separate channel. A filename or an archive's appearance is not evidence of authenticity.

If the file is expected and your policy permits it, use macOS's supported privacy and security workflow to allow that specific application. Do not broadly disable host protection or remove checks from unrelated files to make one command run. A managed machine may require its administrator's approval.

Separate later startup failures ​

Once the executable can run, --help can verify the command interface without starting the server. Server startup then requires existing valid configuration and credentials files. An XML validation error or occupied port is unrelated to the earlier developer-verification warning.

Preserve the exact warning and artifact identity when asking an administrator for help. Database credentials and application records are not needed to investigate whether an executable is trusted.

See installation, command-line options and configuration files.