On Mon, Oct 08, 2018 at 12:53:36PM -0700, Brian W. wrote: Hi there,
> Ok I figured it out. Good stuff. > A page I saw mentioned copying the ldap conf as the > nginx.conf file and using that and I did. I erroneously thought the port > 9000 connection in there was a necessary ldap connect piece and so I didn't > change it, until today with your questioning. Ah, with hindsight, I think I understand what happened. https://github.com/nginxinc/nginx-ldap-auth/blob/master/nginx-ldap-auth.conf shows the backend as both handling /login and providing the common response, while the ldap-auth daemon is separate. And the login service issues a redirect itself. In your case, I guess that the /login-equivalent (if it exists) is *not* on the same server as the backend common content -- so "proxy_pass http://backend/;"; there becomes "proxy_pass http://windows-server/;"; in your case. And hopefully the part with the # in the client-side url Just Works for you too. Glad you got it working, f -- Francis Daly fran...@daoine.org _______________________________________________ nginx mailing list nginx@nginx.org http://mailman.nginx.org/mailman/listinfo/nginx
