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

Problem: Unable to authenticate with LDAP in v2.9.109 #2063

Closed
guyke01 opened this issue May 28, 2024 · 5 comments
Closed

Problem: Unable to authenticate with LDAP in v2.9.109 #2063

guyke01 opened this issue May 28, 2024 · 5 comments
Assignees

Comments

@guyke01
Copy link

guyke01 commented May 28, 2024

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

N/A. Docker installation.

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

{
"ldap_enable": true,
"ldap_needtls": true,
"ldap_binddn": "<REDACTED>",
"ldap_bindpassword": "<REDACTED>",
"ldap_server": "<REDACTED>:636",
"ldap_searchdn": "<REDACTED>",
"ldap_searchfilter": "(&(sAMAccountName=%s)(memberOf:1.2.840.113556.1.4.1941:=CN=<REDACTED>))",
"ldap_mappings": {
"dn": "distinguishedName",
"mail": "mail",
"uid": "sAMAccountName",
"cn": "cn"
},
"access_key_encryption": "<REDACTED>",
"cookie_encryption": "<REDACTED>",
"cookie_hash": "<REDACTED>"
}

Additional information

No response

@fiftin
Copy link
Collaborator

fiftin commented May 29, 2024

Hi @guyke01 thank you.

Reproduced the issue. LDAP with SSL works fine on the host machine, but doesn't work in Docker.

@guyke01
Copy link
Author

guyke01 commented May 29, 2024

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.

@fiftin
Copy link
Collaborator

fiftin commented May 29, 2024

I found out the cause of the problem, it will be fixed ASAP.

@fiftin
Copy link
Collaborator

fiftin commented May 29, 2024

@guyke01 fixed. Pushed v2.9.111-beta.

@guyke01
Copy link
Author

guyke01 commented May 30, 2024

@fiftin Thanks for the rapid fix. Can confirm that LDAP(S) is working again in v2.9.111-beta.

@fiftin fiftin closed this as completed May 30, 2024
truecharts-admin referenced this issue in truecharts/charts May 30, 2024
…@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=-->
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: Done
Development

No branches or pull requests

3 participants