Before you start

verify your environment meets these requirements supported hardware {{k3}} , application version 6 3 1 3 or later, with initial setup completed (including loading a platform master key and network configuration) supported operating systems windows 10 and later linux required access an account on the kmes with administrator permissions to create roles, identities, tls pki, and update system settings local administrator/root access on all hosts where you install or configure components network and firewall allow outbound tcp port 2001 (default host api port) from your self hosted bitwarden server to the kmes series 3, specified by fqdn (for example, kmes example com ) or cidr (for example, 10 0 0 0/24 ) tls inspection or ssl proxies can break mutual tls handshakes exempt the kmes fqdn(s) from inspection configure the kmes series 3 with a fqdn so the exemption applies other openssl bitwarden refer to the bitwarden about key connector article to ensure you understand the requirements for enabling key connector (such as having an enterprise organization, a self hosted bitwarden server, an active sso implementation, and so on)