GitHub user dosubot[bot] added a comment to the discussion: invalid LDAP login 
problem

<!-- Greeting -->
Hey @Mikoakos! I'm here to help you with any bugs, questions, or contributions 
while you wait for a human to assist you. Let's get this sorted out!

<!-- Answer -->
I found a similar unsolved discussion that might be relevant to your issue: 
[Superset docker and LDAP Integration | Unable to get the next page after 
authentication with LDAP](https://github.com/apache/superset/discussions/30018) 
<sup>[[1]](https://github.com/apache/superset/discussions/30018)</sup>. 
Although it doesn't provide a solution, it might offer some insights or 
commonalities with your situation.

Regarding your configuration, here are a few things to check:

1. **LDAP Server and Credentials**: Ensure that the `AUTH_LDAP_SERVER`, 
`AUTH_LDAP_BIND_USER`, and `AUTH_LDAP_BIND_PASSWORD` are correct and have the 
necessary permissions to search the LDAP directory.

2. **Search Filter and UID Field**: Verify that the `AUTH_LDAP_SEARCH_FILTER` 
and `AUTH_LDAP_UID_FIELD` are correctly set to match the attributes used in 
your LDAP directory. The filter `(pertuEmail={username})(uid={username})` 
should match the LDAP entries.

3. **Role Mapping**: Check that the group names in `AUTH_ROLES_MAPPING` match 
exactly with the LDAP group names. Any mismatch can prevent proper role 
assignment.

4. **TLS and Self-Signed Certificates**: Since `AUTH_LDAP_USE_TLS` is set to 
`False`, ensure that your LDAP server does not require TLS. If it does, you 
might need to enable TLS and configure the server to accept self-signed 
certificates if necessary.

5. **Local Database Authentication**: With `AUTH_LDAP_ALLOW_LOCAL_DB` set to 
`True`, ensure that local database authentication is correctly configured and 
that there are no conflicts with LDAP authentication.

6. **Logs**: Check the Superset logs for any LDAP-related errors or warnings 
that might provide more context on the "invalid login" issue.

These steps might help you identify the root cause of the problem.


<!-- Dosu Comment Footer -->
*To continue talking to [Dosu](https://dosu.dev), mention @dosu.*

---
<sup>Help Dosu learn! Give it feedback: [Great 
Response](https://app.dosu.dev/response-feedback/88a023b1-3f50-41bc-bf05-f940244c374d?feedback_type=great_response)
 | [Irrelevant 
Answer](https://app.dosu.dev/response-feedback/88a023b1-3f50-41bc-bf05-f940244c374d?feedback_type=irrelevant_answer)
 | [Incorrect 
Sources](https://app.dosu.dev/response-feedback/88a023b1-3f50-41bc-bf05-f940244c374d?feedback_type=incorrect_sources)
 | [Too 
Verbose](https://app.dosu.dev/response-feedback/88a023b1-3f50-41bc-bf05-f940244c374d?feedback_type=too_verbose)
 | 
[Hallucination](https://app.dosu.dev/response-feedback/88a023b1-3f50-41bc-bf05-f940244c374d?feedback_type=hallucination)
 | [Bug 
Report](https://app.dosu.dev/response-feedback/88a023b1-3f50-41bc-bf05-f940244c374d?feedback_type=bug_report)
 | 
[Other](https://app.dosu.dev/response-feedback/88a023b1-3f50-41bc-bf05-f940244c374d?feedback_type=other)</sup>


GitHub link: 
https://github.com/apache/superset/discussions/32909#discussioncomment-12665527

----
This is an automatically sent email for [email protected].
To unsubscribe, please send an email to: 
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to