-
-
Notifications
You must be signed in to change notification settings - Fork 1k
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
Problem: Unable to authenticate with LDAP in v2.9.109 #2063
Comments
Hi @guyke01 thank you. Reproduced the issue. LDAP with SSL works fine on the host machine, but doesn't work in Docker. |
Hi @fiftin, Good to know that it can reproduced. I've didn't test it on the host itself as you did. Thanks for checking the issue. |
I found out the cause of the problem, it will be fixed ASAP. |
@guyke01 fixed. Pushed |
@fiftin Thanks for the rapid fix. Can confirm that LDAP(S) is working again in |
…@05c9a6f by renovate (#22652) This PR contains the following updates: | Package | Update | Change | |---|---|---| | [semaphoreui/semaphore](https://togithub.com/semaphoreui/semaphore) | patch | `v2.9.75` -> `v2.9.112` | --- > [!WARNING] > Some dependencies could not be looked up. Check the Dependency Dashboard for more information. --- ### Release Notes <details> <summary>semaphoreui/semaphore (semaphoreui/semaphore)</summary> ### [`v2.9.112`](https://togithub.com/semaphoreui/semaphore/releases/tag/v2.9.112) [Compare Source](https://togithub.com/semaphoreui/semaphore/compare/v2.9.75...v2.9.112) #### Bugfixes - Docker: Fixed zombie processes [https://github.com/semaphoreui/semaphore/issues/2069](https://togithub.com/semaphoreui/semaphore/issues/2069) - Docker: Moved Python venv from `~/venv` to `/opt/semaphore/venv` to fix issue [https://github.com/semaphoreui/semaphore/issues/2060](https://togithub.com/semaphoreui/semaphore/issues/2060) - Docker: LDAP issue [https://github.com/semaphoreui/semaphore/issues/2063](https://togithub.com/semaphoreui/semaphore/issues/2063) - UI: Remove extra close button in Template dialog </details> --- ### Configuration 📅 **Schedule**: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined). 🚦 **Automerge**: Enabled. ♻ **Rebasing**: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox. 🔕 **Ignore**: Close this PR and you won't be reminded about this update again. --- - [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check this box --- This PR has been generated by [Renovate Bot](https://togithub.com/renovatebot/renovate). <!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiIzNy4zODIuMCIsInVwZGF0ZWRJblZlciI6IjM3LjM4Mi4wIiwidGFyZ2V0QnJhbmNoIjoibWFzdGVyIiwibGFiZWxzIjpbImF1dG9tZXJnZSIsInVwZGF0ZS9kb2NrZXIvZ2VuZXJhbC9ub24tbWFqb3IiXX0=-->
Issue
After updating to version v2.9.109 it is not possible anymore to use LDAP Authentication. When TLS is turned on with port 636 a error message 500 will show up at the login page.
When changing TLS to off and change the port to 389 there is a incorrect username or password. When i revert to version v2.9.75 the LDAP connections works with TLS enabled and port 636 configured.
Impact
Web-Frontend (what users interact with)
Installation method
Docker
Database
MySQL
Browser
Microsoft Edge
Semaphore Version
v2.9.109
Ansible Version
Logs & errors
time="2024-05-28T05:12:28Z" level=warning msg="unable to read LDAP response packet: read tcp <REDACTED>:44374-><REDACTED>:636: read: connection reset by peer"
Manual installation - system information
No response
Configuration
Additional information
No response
The text was updated successfully, but these errors were encountered: