Credentials and remote deployment

The local runner and server accept --credentials-file private.json. This file maps a credentialRef in the lab definition to a native configuration XML overlay. It replaces credentials in memory without editing the source asset. Protect the file and never place real credentials in scripts or reports.

{"test-device":"<SnmpAgent><context id=\"context-0\" readCommunity=\"test-read\" writeCommunity=\"test-write\"/></SnmpAgent>"}

The example credentialRef is test-device. For multiple recordings, supply every required context. An empty writeCommunity disables SET in that context. SNMPv3 overlays use the existing user, group, view, and optional properties elements described in the configuration chapter. Engine boots remain managed by the service.

Headless automation rejects recordings containing BeanShell scripts unless you explicitly add --trusted-scripts. Enable this only for recordings you trust: scripts execute with the service account privileges and can run external or blocking commands. Desktop scripts retain their existing behavior.

LAN management can use HTTP with --bind and the service interface address. Optional HTTPS uses --tls-keystore with a PKCS12 keystore and --tls-password-file with its password file. For HTTPS, connect with https and validate the certificate.

If you have a packaged Release 1 container image, mount a writable workspace at /work and mount license and credential files read-only under /run/secrets. The supplied image uses UID/GID 10001, so make the workspace writable by that account. Its default management listener is container loopback. To accept other containers, bind management explicitly with --bind 0.0.0.0 (and optional HTTPS).

SNMP agent addresses must also bind to 0.0.0.0 or a container interface for traffic arriving from outside the container. Management uses TCP; SNMP uses UDP. Publish only the ports you need. Twenty ports on one container address represent twenty SNMP endpoints, not twenty separately discoverable IP addresses. Keep the management endpoint private unless protected by HTTPS.

For normal desktop use, continue with the graphical-interface instructions earlier in this guide. For XML scripts, recording formats, and SNMPv3 configuration details, see Helper Functions, SNMP Walk Data File, SNMP Trap Data File, and Simulator Configuration.