07-05-2018 12:39 PM
Hello. Is it supported to run the proxy directly on the domain controller? I’m trying to minimize the server foot print.
I have everything configured for LDAP and connectivity checks out ok via the connectivity_tool. The log does tell me that obviously something is already bound to 389. Is it possible to change the port the duo listens on? I can then specify the port in my client config.
Solved! Go to Solution.
07-06-2018 06:49 AM
We do not recommend this for a variety of reasons, one being the issue you describe (where ports are already in use).
You can change the port that the Duo proxy uses for incoming LDAP requests in the authproxy.cfg
file using the port=
setting, which is mentioned in that KB article linked above and also documented in the Duo Authentication Proxy reference.
07-06-2018 06:49 AM
We do not recommend this for a variety of reasons, one being the issue you describe (where ports are already in use).
You can change the port that the Duo proxy uses for incoming LDAP requests in the authproxy.cfg
file using the port=
setting, which is mentioned in that KB article linked above and also documented in the Duo Authentication Proxy reference.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide