@Prashant_Shandilya the ldap auth plugin only has consumer mapping in the Enterprise edition with LDAP Auth Advanced Plugin via the config.consumer_by property. With the LDAP plugin, you can only bind to an anonymous consumer. There is future support for LDAP<->ACL planned via authenticated_groups context (https://github.com/Kong/kong/pull/4013), but for now the community edition lacks this support.
This feature is very much required and since external authentication and autherization matix implementation are standard use cases. If this basic is not supported, its would be very difficult to adopt Kong.
What is the plan to include pull requests mentioned in previous comments ?
Kong EE does not lack the support that @Prashant_Shandilya originally is referring to, where a service/ route is mapped by the LDAP Auth Advanced plugin to a Consumer who is part of an ACL group.
But it does currently lacks the authenticated_groups context PR 4013 that I mentioned, which is for when you do not even need a Kong Consumer. I cannot comment with any certainty on how soon 4013 will be available for usage with the LDAP Auth Advanced plugin, but I do know that it is planned for this year sometime.