
Using LastPass? You need to switch urgently, says security firm Hackers dug deep in the massive LastPass security breach The DNS-records for this domain must point to the Connect server.Īs long as Connect is running, its HTTPS listener must be reachable on a public IP at port 443 (either by setting OP_HTTPS_PORT=443 or by forwarding traffic at port 443 to Connect's OP_HTTPS_PORT) for the server to be able to refresh its Let's Encrypt certificate.NordPass adds passkey support to banish your weak passwords

This can be done either by providing your own certificate or by letting Connect request a certificate using Let's Encrypt.Ĭonnect will listen on the port defined by OP_HTTPS_PORT (default 8443) when TLS is enabled.Ĭonnect can use a PEM-encoded private key and certificate by setting the following two environment variables for the connect-api container: It is possible to enable TLS for the connection between your application and Connect. More information on configuration options TLSīy default, 1Password Connect is configured for use within a trusted network. OP_SYNC_TIMEOUT: define how long to wait for initial sync to complete.OP_HTTPS_PORT: port used by the HTTP sever when TLS is configured (see below).Defaults to info.Īll other configuration options are only relevant for the password/connect-api container: OP_LOG_LEVEL: set the logging level of the container.OP_HTTP_PORT: port used by the HTTP server.Defaults to ~/.op/1password-credentials.json. OP_SESSION: path to the 1password-credentials.json file.

The following environment variable configuration options are available for both containers:

1password/connect-api: serves the Connect REST API.

