I don't libgssapi works on windows. However windows supports this auth mechanism via SSPI. See:

http://msdn.microsoft.com/en-us/library/aa380496%28VS.85%29.aspx

And Winsspi is built into curl on windows. Did you try it? or is it what you are looking for?

If it would work with winsspi then we should be able to set CURLAUTH_GSSNEGOTIATE as CURLOPT_HTTPAUTH option in cURL. But if we do so, false gets returned and we aren't able to delegate the authorization token of the client.

I don't understand what you are saying sorry.


Does it work? If not, what does not work exactly (like the constants are not defined or the required protocols are not listed in the available features, via curl info)? The options are not available? or they are not used even when you set them?

It doesn't work in my opinion. The option CURLOPT_HTTPAUTH can have multiple authentication types like CURLAUTH_BASIC (value), *NTLM, as well as CURLAUTH_GSSNEGOTIATE - which is used to authenticate with kerberos. When we set this option/auth type [curl_setopt(CURLOPT_HTTPAUTH, CURLAUTH_GSSNEGOTIATE)] we get false as return value - which means that GSSAPI (or SSPI) is not available and this property can not be used with the cURL extension.

Please see http://www.php.net/curl_setopt (CURLOPT_HTTPAUTH)

Did you try ANY_SAFE or using the bitwise operator for ntlm and GSS?

I suppose too that it is only in your comment that the curl_setopt misses the curl resource.

NTLM is working, but GSS not. We allready tried that. But we need kerberos authentication - that's why we need gssnegotiate to work.

in addition to understand our problem, you can visit another feature/change request located here: http://bugs.php.net/bug.php?id=52231

ok, I don't seem to be able to get the details I need to actually see where is the point of failure.

I do not use kerberos, so I won't be able to test or debug it. However, if you can provide me an access to a box where I can actually test GSS for kerberos auth, then we may get one step further.

By the way, one thing that could help is to test using the curl command line tool. All features available through the API can be tested using the command line as well (see the curl website). Can you give it a try too please?

About soap, unrelated. Soap does not use Curl.

I'll try your suggestion and give you feedback.
Why I posted this link is not because of soap. Please read the last paragraph about overriding __doRequest and rebuilding it with cURL. Maybe you can extract some usefull information about our problem or about our environment.

Is this issue still unresolved?  It seems to me that the provided
libcurl builds have SSPI enabled for many years, and according to
the cURL documentation[1], CURLAUTH_NEGOTIATE requires SSPI on
Windows.

[1] <https://curl.se/libcurl/c/CURLOPT_HTTPAUTH.html>

No feedback was provided. The bug is being suspended because
we assume that you are no longer experiencing the problem.
If this is not the case and you are able to provide the
information that was requested earlier, please do so and
change the status of the bug back to "Re-Opened". Thank you.