-
Notifications
You must be signed in to change notification settings - Fork 441
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
[Bug]: internal server error when using ldap to login #7959
Comments
Hi, I had exactly the same issue. after some research, it seem that it was a go issue. hope this will help, |
to be frank if error related to memory addresses inside application can be triggered by specific client/browser request this issue should have higher priority ;) |
@jacekjaros when I follow our own guide https://zitadel.com/docs/guides/integrate/identity-providers/openldap to setup LDAP, using a fresh zitadel v2.51.4 and default config, I'm unable to reproduce your issue. Looking at the line that created the panic:
It could be that somehow Can you run the following query in the zitadel database to check the state (replace select i.id, i.name, l.idp_id, l.bind_password
from projections.idp_templates6 i
left join projections.idp_templates6_ldap2 l on l.idp_id = i.id
where i.name = 'OpenLDAP'; With my setup the output looks like:
|
hi @muhlemmer, you are right about empty password in my setup.
let me check with configuration, with added bind password. i will post update after test. thanks, |
Preflight Checklist
Environment
Self-hosted
Version
v2.51.4
Database
PostgreSQL
Database Version
16.3
Describe the problem caused by this bug
i add ldap IDP. whan go to login page and hit Login with an external user -> ldap i get empty response to broswer and i see following error in docker logs:
To reproduce
on fresh instance:
Screenshots
Expected behavior
one of:
Operating System
dockers from official repo working on latest ubuntu lts
Relevant Configuration
ldap config are attached in screenshots
Additional Context
No response
The text was updated successfully, but these errors were encountered: