[
https://issues.apache.org/jira/browse/HTTPCLIENT-1912?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16577360#comment-16577360
]
Michael Osipov commented on HTTPCLIENT-1912:
--------------------------------------------
HttpClient provides an authenticator for that, but it is broken. You should
disable it with a custon {{AuthSchemeFactory}}. I assumed that you wanted to
hook in your custom factory. If you don't, that's fine.
The curl code isn't fine either:
{noformat}
[mosipov@mika-ion ~/Projekte/curl/lib/vauth]$ grep -r S_CONTINUE .
[mosipov@mika-ion ~/Projekte/curl/lib/vauth]$ grep -r S_COMPLETE .
./spnego_gssapi.c: if(nego->context && nego->status == GSS_S_COMPLETE) {
{noformat}
> AuthSchemes.SPNEGO should be able to specify login conf and krb5 conf as
> parameters instead of system properties
> ----------------------------------------------------------------------------------------------------------------
>
> Key: HTTPCLIENT-1912
> URL: https://issues.apache.org/jira/browse/HTTPCLIENT-1912
> Project: HttpComponents HttpClient
> Issue Type: Improvement
> Components: HttpClient (classic)
> Affects Versions: 4.5.2
> Reporter: Nicholas DiPiazza
> Priority: Major
> Labels: volunteers-wanted
> Fix For: Stuck
>
>
> in order to use spenego
> see
> [example|https://github.com/jumarko/kerberos-auth-example/blob/master/src/main/java/net/curiousprogrammer/auth/kerberos/example/KerberosAuthExample.java]
> you need to specify system properties to specify a custom krb5.conf or
> login.conf location.
> It would be very useful if these could be given as parameters somehow instead
> of system properties, because in our cloud apps use case, sharing these as
> system properties at the jvm level is causing conflicts.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
