Authenticated Proxies Support about duo_client_python

[DuoKristina]

Hi matc,

You're right, this demonstration client doesn't include support for an authenticated proxy. You're welcome to fork and include support for those headers.

[matc]

Hi Kristina,

Thanks for the quick response and for looking into this for me. I will take a look tomorrow to evaluate forking this Duo client vs building new with proxy auth on a more generic client and follow up. Closing out this ticket now :)

Thanks again!
Mat

[BradleyHiggins]

This worked for me, using basic auth with a squid3 proxy:

auth_api.set_proxy('myproxy.local.net',
        port='8080',
        headers={
            "Proxy-Authorization":
            "Basic " + base64.b64encode(b"proxyUsername:proxyPassword").decode("utf-8")
        },)

Set the headers param in the set_proxy call, which expects a dictionary. Keys are HTTP Header names, and values are the associated header value. I tested this with python 3. You may need to tweak it for python 2.

This will work with a CONNECT proxy only. Duo's API code wants to directly validate the SSL connection to Duo's servers (instead of trusting the proxy to validate the upstream connection). HTTP CONNECT helps accomplish that.

If the connection between your API and proxy is (non-SSL) HTTP, be aware that this will put the proxy user's password on the network. The HTTPS connection end-to-end between the API client and Duo's server will still be secure, even with a (non-SSL) HTTP proxy.

[matc]

@BradleyHiggins - this worked beautifully on python 2!! Thank you so much for sharing this with me 🥇👏🏼
Really appreciate you help here, saved me quite a significant amount of work!