Heads Up :
The post you are writing will appear in a public forum. Please ensure all content is appropriate for public consumption. Review the employee guidelines for the community here.
The popup up mentioned here: Knowledge Base | Duo Security
Is there any known way to suppress it and return to the previous functionality? I know this is likely a Chrome question more than a Duo question but I’m hopeful someone here has encountered i...
Is there any way to get the Duo Proxy service to pass either the IP address of the LDAP client or some sort of friendly name to the application endpoint? We have a number of services passing through the proxy and there’s currently no way to discern w...
All of the documented functions for retrieving bypass codes include the following note: “Does not return the actual bypass codes.” The Admin panel clearly allows you to show the existing codes. How do you retieve them with the Admin API?
I integrated duo to several of our web applications successfully some months back. I recently got our Duo proxy server set up and I want to convert some of our sites to use the HTTP Proxy function rather than pointing directly to Duo. I thought that ...
I found a different solution that doesn’t require changing the entire stack to async calls. In our case we couldn’t do so because then you can’t access session data.
var token = Task.Run(async () =>
{
return await duoClient.ExchangeAu...
Isn’t the source IP you see the IP address of the LDAP application that is communicating with the authentication proxy
It is the address of the LDAP application and that’s actually what we are looking for. We have a significant number of LDAP clien...
That makes sense but the source IP does appear in the authproxy.log file which means the auth proxy service is at least aware of the source regardless of the LDAP RFC:
2020-05-05T10:14:07-0400 [duoauthproxy.modules.ad_client._ADServiceClientFactory#i...
