> For the complete documentation index, see [llms.txt](https://docs.bindplane.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.bindplane.com/changelog/july-2024/2024-07-01-release.md). # 2024-07-01-Release Version 1.62.0 • JUL 01, 2024 ## New Features * New [init ldap](#init-ldap) CLI command, for configuring and migrating authentication to ldap ## Bug Fixes * Return 401 for missing account header (measurements) * Enforce NATS mutual TLS * Conditional Builder Regex escaping * See [Upgrade Procedure](#upgrade-procedure) section. ### Init LDAP When operating BindPlane OP on Linux, you can migrate to LDAP by executing the following command on the Linux server. ```bash sudo BINDPLANE_CONFIG_HOME=/var/lib/bindplane \ /usr/local/bin/bindplane init ldap \ --config /etc/bindplane/config.yaml ``` The command will prompt for your ldap server information, and migrate your BindPlane accounts to the new authentication mechanism. ### Upgrade Procedure After upgrading to BindPlane v1.62.0, review your configurations for pending rollouts. Update any configurations that contain processors with conditions built using the condition builder. Previous versions of BindPlane will have required the user to handle regex escaping on their own. v1.62.0 handles the escaping for you, however, existing conditions will need to be updated to take this into account. --- # 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.bindplane.com/changelog/july-2024/2024-07-01-release.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.