> For the complete documentation index, see [llms.txt](https://docs.keeper.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.keeper.io/release-notes/enterprise/bridge/bridge-version-18.0.0.md). # Bridge Version 18.0.0 Released on October 29, 2026 ### Overview Keeper Enterprise Bridge 18.0.0 is a feature and security release. It adds support for Keeper Outpost, makes Bridge configuration and stored credentials more secure, and removes support for OpenLDAP directories. All Keeper Enterprise Bridge deployments should be upgraded to version 18.0.0 as soon as possible, or during the next scheduled maintenance window. **Important:** OpenLDAP is no longer supported as a directory source in Keeper Enterprise Bridge 18.0.0. Customers who sync from OpenLDAP should review their provisioning setup before upgrading. ### New Features * **EB-490: Support** for [Self-Managed Keeper](https://www.keepersecurity.com/self-managed-keeper/) tenants. ### Improvements * **EB-495: Configuration Reset Hardening** The Bridge no longer uses a `settings.reset` file on disk to reset its configuration. Placing a file on the Bridge host can no longer clear the Bridge directory connection settings. * **EB-496: OpenLDAP Support Removed** Support for OpenLDAP directories has been removed from the Bridge. ### Security Updates * **EB-493: Service Endpoint Hardening** The local communication channel between the Bridge client and the Bridge service has been secured. Only the legitimate Bridge service can listen on the endpoint, and the client checks the identity of the service before it sends any credentials. This prevents another local process from impersonating the Bridge service. * **EB-491: Protection of Enrollment Credentials** The Bridge now stops enrollment if the configuration protection key is not available. It no longer writes administrator device credentials unprotected. A reconnected client session must be authorized again before it can use privileged operations. File system permissions on the Bridge configuration file and data folder have been tightened so that unprivileged local accounts cannot read them. Login resumption codes are now removed on every enrollment exit path. * **EB-492: Removal of Legacy Value Obfuscation** The legacy compatibility code that loaded obfuscated, unencrypted values from the Bridge service configuration has been removed. Stored service values are now accepted only when they are encrypted. * **EB-494: Service Stability Hardening** Fixed an unhandled error in the Bridge service polling cycle that could stop the service under certain conditions, such as an empty or invalid directory configuration. This improves the service's resistance to denial-of-service conditions. ### Update Instructions * Download the latest Keeper Enterprise Bridge installer and run it on the Bridge host to upgrade the existing installation. Then restart the Keeper Bridge service. * After upgrading, open the Bridge client and check that the Bridge is connected to your directory and to Keeper and that sync runs normally. * If your environment used the `settings.reset` file to reset Bridge settings, that method no longer works. Reset the configuration from the Bridge client as described in the Keeper Enterprise Bridge documentation. * If your directory source is OpenLDAP, do not upgrade until you have moved provisioning to a supported directory or another Keeper provisioning method. ### Resources * [Keeper Bridge guide](https://docs.keeper.io/keeper-bridge/) --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.keeper.io/release-notes/enterprise/bridge/bridge-version-18.0.0.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.