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

Add support for connecting to multiple LDAP hosts #564

Merged

Conversation

nk540347
Copy link

…pace-separated host strings

This update enhances the LDAP client by allowing it to connect to multiple LDAP servers. The 'Host' field now accepts a space-separated string of LDAP host addresses. The Connect method iterates over these hosts, attempting to establish a connection with each one until a successful connection is made.

Key changes:

  • Split the 'Host' field into individual host addresses.
  • Iterated over each host to attempt a connection.
  • Implemented error handling to try the next host if a connection fails.
  • Updated the connection logic to support both non-SSL and SSL connections, including handling TLS upgrades.

This change improves the robustness of the LDAP client by ensuring that the application can failover to another LDAP server if the primary server is unavailable.

…pace-separated host strings

This update enhances the LDAP client by allowing it to connect to multiple LDAP servers. The 'Host' field now accepts a space-separated string of LDAP host addresses. The `Connect` method iterates over these hosts, attempting to establish a connection with each one until a successful connection is made.

Key changes:
- Split the 'Host' field into individual host addresses.
- Iterated over each host to attempt a connection.
- Implemented error handling to try the next host if a connection fails.
- Updated the connection logic to support both non-SSL and SSL connections, including handling TLS upgrades.

This change improves the robustness of the LDAP client by ensuring that the application can failover to another LDAP server if the primary server is unavailable.
@CLAassistant
Copy link

CLA assistant check
Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.


Nausherwan Khan seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.
You have signed the CLA already but the status is still pending? Let us recheck it.

@adubovikov
Copy link
Member

Thank you! Looks good for me

@adubovikov adubovikov merged commit 60b96a6 into sipcapture:master Aug 30, 2024
2 of 3 checks passed

// Reconnect with TLS
if !lc.SkipTLS {
err = l.StartTLS(&tls.Config{InsecureSkipVerify: true})

Check failure

Code scanning / CodeQL

Disabled TLS certificate check High

InsecureSkipVerify should not be used in production code.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants