[
https://issues.apache.org/jira/browse/HTTPCLIENT-1394?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ryan McKinley updated HTTPCLIENT-1394:
--------------------------------------
Attachment: HTTPCLIENT-1394-jna.patch
here is a cleaned up patch that fixes many style issues (passes
maven:checkstyle)
Sebb, this sorts out the issues you point out except:
bq. some classes use @SuppressWarnings
The deprecation is copied from the other SchemaFactories. At 4.3, things are
moving from AuthSchemeFactory to AuthSchemeProvider but should keep working for
things that use AuthSchemeFactory
----
I made JNA an optional dependency. This means it is around for compile time,
but people have to explicitly add it if they want to use the windows thing.
to test if the JNA schema will work, people could use:
WindowsNegotiateScheme.isAvaliable()
-----
I still need to look into testing
> Native windows Negotiate/NTLM via JNA
> -------------------------------------
>
> Key: HTTPCLIENT-1394
> URL: https://issues.apache.org/jira/browse/HTTPCLIENT-1394
> Project: HttpComponents HttpClient
> Issue Type: New Feature
> Environment: Windows
> Reporter: Ryan McKinley
> Attachments: HTTPCLIENT-1394-jna.patch, HTTPCLIENT-1394-jna.patch
>
>
> HttpClient has made great progress in supporting NTLM and Negotiate, but the
> setup often requires considerable configuration. Using native calls, we can
> authenticate the current logged in user directly via windows with no
> configuration.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
