-
Notifications
You must be signed in to change notification settings - Fork 102
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
http proxy negotiate/gssapi authentication? #83
Comments
requests-kerberos cannot currently handle that kind of authentication. |
Thank you for clarifying. Is it proxy auth something that belongs in this project, or am I barking up the wrong tree? |
It definitely belongs in this project. =) Unfortunately, I have very little time to tackle writing such a thing, so I'll have to leave this open to someone else who can find that time. |
This would be nice to have! However, Requests doesn't support multiple auth handlers, so it can be a problem if you want to use one auth method for the proxy, and another for the actual request. This is already an issue with HttpNtlmAuth from requests-ntlm, though I don't know if the problem's tracked anywhere. HttpNtlmAuth also handles NTLM authentication for either a proxy or a website, based on what response header it sees first, which makes it a bit of an oddball. |
Hi everyone! Any ideas how the proxy auth can be done with requests-kerberos? |
When I use IP address as the auth surrogate in the proxy the following works, however, when I use no surrogate it doesn't work. Just sharing the code in case it'll help others. |
@NurcanSonmez , Thanks for your code, it was very useful for me when I just ran into this problem. But with requests https, it really doesn't work. Having studied the code of Requests, I realized that the authentication data (that was placed in the request header) does not reach the method "set_tunnel" (module httplib(py2)/http.client(py3)). I used the following code to solve this problem:
Maybe it will be useful for someone. |
Support for proxying |
I was hoping to find a
HTTPProxyKerberosAuth
class to enable working with http proxies that require NEGOTIATE gssapi auth, like certain configurations of squid. Is there a way to use requests-kerberos handle that scenario as it currently stands?This would be akin to HTTPProxyDigestAuth from requests-toolbelt, if the necessary code doesn't already exist somewhere.
The text was updated successfully, but these errors were encountered: