[ 
https://issues.apache.org/jira/browse/HTTPCLIENT-523?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12709860#action_12709860
 ] 

Marko Asplund commented on HTTPCLIENT-523:
------------------------------------------

I think SPNEGO support would be a very important thing to have in order to be 
able to talk to Windows based servers. I'm currently trying to integrate a Java 
based web application with Microsoft Sharepoint server and authentication has 
proven to be the trickiest part. HttpClient 3.1 only seems to support NTLM v1 
which is not enabled by default on Windows servers and administrators don't 
usually allow using it.

NTLM autentication works well with HttpClient 4.0 + JCIFS but in many cases 
SPNEGO / Kerberos would be much better choice due because many Windows server 
administrators prefer that nowadays and because of features such as credential 
delegation that are extremely useful in many web applications.


> SPNEGO authentication scheme
> ----------------------------
>
>                 Key: HTTPCLIENT-523
>                 URL: https://issues.apache.org/jira/browse/HTTPCLIENT-523
>             Project: HttpComponents HttpClient
>          Issue Type: Improvement
>          Components: HttpAuth
>    Affects Versions: Snapshot
>         Environment: Operating System: All
> Platform: All
>            Reporter: Mikael Wikström
>            Priority: Minor
>             Fix For: Future
>
>         Attachments: bcsLogin.conf, 
> CustomAuthenticationNegotiateExample.java, 
> CustomAuthenticationNegotiateExample.java, NegotiateScheme.java, 
> NegotiateScheme.java, run.sh, submitclient.tar.gz
>
>
> Consider integrating the SPNEGO auth scheme from Commons HttpClient contrib 
> package into HttpClient 4.0

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to