I think I'm missing something here. E456 uid can't login to elasticsearch even if it is a member of ou=people,ou=ec,o=world. But when using E123 uid, it is successful. E456 and E123 belongs to the same group btw.
You'll need share more information for any meaningful diagnosis, e.g. what is the exact error, (401 or 403?), server side trace or debug logs for the failure and success scenarios, exact how you entered the username for authenticating and perhaps the authenticate response from the successful user.
You should check what you get in the Authenticate API response. The user's ldap groups are listed in the metadata. My guess is that the groups do not match ou=people,ou=ec,o=world which is why the entry is not working.
Still stuck. But here's a new log in elasticsearch. You can see it is auth successful. But still having error like above screenshot.
[2022-10-17T14:23:58,629][DEBUG][o.e.x.s.a.RealmsAuthenticator] [host] Authentication of [E456] using realm [ldap/ldap01] with token [UsernamePasswordToken] was [AuthenticationResult{status=SUCCESS, value=User[username=E456,roles=[],fullName=null,email=null,metadata={ldap_dn=uid=E456,ou=people,ou=ec,o=world, ldap_groups=[]}], message=null, exception=null}]
Yeah the issue is with authorization (role mapping), not authencation. Based on the log message, it is clear that your E456 user does not have any ldap groups
Maybe this user does not have permission to perform group search. Or maybe you should search group in higher level, i.e. instead of
Apache, Apache Lucene, Apache Hadoop, Hadoop, HDFS and the yellow elephant
logo are trademarks of the
Apache Software Foundation
in the United States and/or other countries.