You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I realize this is less likely an issue an more likely something with my config, but hopefully someone can set me straight.
Everything is working correctly as far aw connectivity, authentication, searches, etc. However, I'm seeing a lot of traffic between nginx and my OpenLDAP server even with caching enabled, and I just want to know if I'm doing something wrong.
Working from the LDAP server backwards, I've got OpenLDAP running in docker. I have a read-only bind_dn account configured, requests from both ldapsearch and nginx with nginx-auth-ldap are working correctly.
In my nginx.conf, in the http section, I have this:
In the rest of my nginx.conf file I have nginx set up to do reverse proxy for an Elasticsearch instance. Then, on the client side, I have several Elastic beats configured to connect to nginx over https, authenticating with credentials that match those stored on the OpenLDAP server.
So, like I said before, everything "works." The beats clients connect, nginx authenticates through nginx-auth-ldap to my ldap server, proxying works correctly, the beats' data gets written to elasticsearch. The only problem, if it is a problem, is I see this in the log of my OpenLDAP server:
I observe the same situation in my configuration. A lot of bindings to LDAP without any further action. Does anybody has an idea about the reason behind this behavior?
I realize this is less likely an issue an more likely something with my config, but hopefully someone can set me straight.
Everything is working correctly as far aw connectivity, authentication, searches, etc. However, I'm seeing a lot of traffic between nginx and my OpenLDAP server even with caching enabled, and I just want to know if I'm doing something wrong.
Working from the LDAP server backwards, I've got OpenLDAP running in docker. I have a read-only bind_dn account configured, requests from both
ldapsearch
andnginx
withnginx-auth-ldap
are working correctly.In my nginx.conf, in the
http
section, I have this:In the rest of my nginx.conf file I have nginx set up to do reverse proxy for an Elasticsearch instance. Then, on the client side, I have several Elastic beats configured to connect to nginx over https, authenticating with credentials that match those stored on the OpenLDAP server.
So, like I said before, everything "works." The beats clients connect, nginx authenticates through nginx-auth-ldap to my ldap server, proxying works correctly, the beats' data gets written to elasticsearch. The only problem, if it is a problem, is I see this in the log of my OpenLDAP server:
That is one second's worth of logs. As you can see in my config file, caching is enabled:
Am I misunderstanding the point of the
auth_ldap_cache_enabled
directive? Is this no big deal, or should I be concerned? Any advice?The text was updated successfully, but these errors were encountered: