dosubot[bot] commented on issue #32165:
URL: https://github.com/apache/superset/issues/32165#issuecomment-2639479790

   <!-- Greeting -->
   Hey there, @amoi-amoi! I'm here to help you with your Superset LDAP 
authentication issue. Let's work together to get this sorted out.
   
   <!-- Answer -->
   I found a similar unsolved discussion that might be relevant to your issue: 
[Assign superset roles to Keycloak authenticated users using the 
AUTH_ROLES_MAPPING](https://github.com/apache/superset/discussions/27902) 
<sup>[[1]](https://github.com/apache/superset/discussions/27902)</sup>.
   
   Regarding your issue with `AUTH_ROLES_MAPPING`, it seems like the mapping is 
not functioning as expected when using the `memberUid` attribute. 
Unfortunately, I couldn't find specific information on how Superset handles 
LDAP group membership when the `AUTH_LDAP_GROUP_FIELD` is set to `memberUid`. 
However, here are a few things you might want to check or try:
   
   1. **Verify LDAP Group Field**: Ensure that the `AUTH_LDAP_GROUP_FIELD` is 
correctly set to the attribute that contains the group membership information. 
In your case, it is set to `memberUid`, which should match the attribute used 
in your LDAP server for group membership.
   
   2. **Check LDAP Group Membership**: Confirm that the users are indeed 
members of the LDAP groups specified in your `AUTH_ROLES_MAPPING`. You can do 
this by querying your LDAP server to see if the `memberUid` attribute lists the 
correct users.
   
   3. **Superset Logs**: Check the Superset logs for any errors or warnings 
related to LDAP authentication and role mapping. This might provide more 
insight into what is going wrong.
   
   4. **Configuration Consistency**: Double-check your configuration for any 
typos or inconsistencies, especially in the distinguished names (DNs) used in 
`AUTH_ROLES_MAPPING`.
   
   If these steps do not resolve the issue, you might need to explore further 
into the Superset codebase or consider reaching out to others who might have 
faced similar issues.
   
   
   <!-- 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/23776a68-6006-4ce1-9135-e94cb374b752?feedback_type=great_response)
 | [Irrelevant 
Answer](https://app.dosu.dev/response-feedback/23776a68-6006-4ce1-9135-e94cb374b752?feedback_type=irrelevant_answer)
 | [Incorrect 
Sources](https://app.dosu.dev/response-feedback/23776a68-6006-4ce1-9135-e94cb374b752?feedback_type=incorrect_sources)
 | [Too 
Verbose](https://app.dosu.dev/response-feedback/23776a68-6006-4ce1-9135-e94cb374b752?feedback_type=too_verbose)
 | 
[Hallucination](https://app.dosu.dev/response-feedback/23776a68-6006-4ce1-9135-e94cb374b752?feedback_type=hallucination)
 | 
[Other](https://app.dosu.dev/response-feedback/23776a68-6006-4ce1-9135-e94cb374b752?feedback_type=other)</sup>
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


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

Reply via email to