I have created a consumer with username=XXX and custom.id=XXX and attached to him the rate-limit plug-in.
Then I have set the global LDAP authentication plugin name=“ldap-auth”. The ldap-auth plug-in works well having
“Authentication base64(username:password)” headers. But it seems that the “username=XXX” is not matched with the consumer XXX as rate-limits are not applied.
I have created the rate-limit plug-in with the following request:
Actually, the referenced example above with httpbin API worked for me in the end.
So then I mounted into it my application and it worked as well.
But then I added the “ldap-auth” plug-in and I got to the problem that I described here.
Isn’t it a bug? I didn’t read anywhere that it cannot be used together.
yes, i was using LDAP auth with Key auth and rate limiting at the same time.
I’ve tried LDAP auth globally and also on a route only.
I am actually using Authorization LDAP base64(username:password) header.
I’ve tried also to configure Key auth’s key as “Authorization” storing the “LDAP base64(username:password)” on the consumers/USERID/key-auth directly but having LDAP auth plug-in anywhere causes that the rate-limiting is not properly evaluated for the consumer.
What I see as a problem is that I will have to provision users’ credentials in to Kong DB in order to be able to use rate-limits per client/consumer. Then the LDAP plugin is useless. One authentication is enough.