-
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
SPNEGO support #116
Comments
@pu239ppy have you looked at https://github.com/pythongssapi/requests-gssapi which is a fork off this repo but uses python-gssapi as the kerberos library instead of pykerberos. My view is that there's not much of an appetite to continue adding new features to requests-kerberos unless it is really needed rather keep it running for applications who haven't moved off it yet. |
@jborean93 thank you, I will give that a try. |
python-gssapi does not include SPNEGO support, so I cannot select it as a mech |
Hi, I'm also a co-author of python-gssapi. That particular issue only refers to the SPNEGO-specific GSSAPI functions to control the mechlist. General SPNEGO works fine with python-gssapi (unless someone knows something I don't). And if you need those functions, we can implement them; they're just not generally useful. |
I can second that, I've used the raw python-gssapi library to work with SPNEGO token with success. It would just require requests-gssapi to expose the functionality to specify the mech to use. |
The original issue was due to a very pedantic configuration on a web server where it expected a SPNEGO OID where as requests-kerberos and requests-gssapi sends a Kerberos OID. This was easy enough to fix in requests kerberos as kerberos supports SPNEGO Authentication where as the gssapi module does not. Regardless, this has since been fixed and this issue along with accompanying PR is no longer required |
I would add one more thing: since it seems to be the desire of the project maintainers to unwind this project, please do the following. Mark it as |
Currently I need to be able to specify SPNEGO OID to a remote end point I have submitted #115 and also there is #89 to accomplish this goal. Any chance that any of these could be merged?
The text was updated successfully, but these errors were encountered: