Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Re-introduce ldap.ssl-trust-certificate as legacy config #12187

Merged
merged 2 commits into from May 9, 2022

Conversation

Praveen2112
Copy link
Member

Description

LDAP Config ldap.ssl-trust-certificate was replaced by ldap.ssl.truststore.path in 376. So this PR updates the release notes in 376 and also additionally adds ldap.ssl-trust-certificate as a legacy config.

Is this change a fix, improvement, new feature, refactoring, or other?

Refactoring

Is this a change to the core query engine, a connector, client library, or the SPI interfaces? (be specific)

A config rename

How would you describe this change to a non-technical end user or system administrator?

Re-introduce ldap.ssl-trust-certificate as legacy config

Related issues, pull requests, and links

Documentation

(x) No documentation is needed.
( ) Sufficient documentation is included in this PR.
( ) Documentation PR is available with #prnumber.
( ) Documentation issue #issuenumber is filed, and can be handled later.

Release notes

( ) No release notes entries required.
(x) Release notes entries required with the following suggested text:

# Section
* Re-introduce ldap.ssl-trust-certificate as legacy config

@Praveen2112 Praveen2112 force-pushed the praveen/100/ldap_re_cleanup branch 2 times, most recently from 9046562 to 1acdb79 Compare May 5, 2022 09:41
@Praveen2112
Copy link
Member Author

@mosabua AC

@Praveen2112 Praveen2112 force-pushed the praveen/100/ldap_re_cleanup branch 2 times, most recently from 2d7de51 to 147115d Compare May 6, 2022 13:28
@Praveen2112 Praveen2112 force-pushed the praveen/100/ldap_re_cleanup branch from 147115d to 7797c7f Compare May 9, 2022 05:29
@Praveen2112 Praveen2112 merged commit 2bb759c into trinodb:master May 9, 2022
@github-actions github-actions bot added this to the 381 milestone May 9, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

Successfully merging this pull request may close these issues.

None yet

4 participants