[
https://issues.apache.org/jira/browse/HTTPCLIENT-1912?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16577354#comment-16577354
]
Nicholas DiPiazza commented on HTTPCLIENT-1912:
-----------------------------------------------
I'm confused. I'm not using HttpClient's auth configs at all. I'm just
generating my own Negotiate token using the JRE's GSS library. Once I have this
token I can just set it as a header on any request even with postman.
For example it generates a token like
{code}
YIILJAYGKwYBBQUC....30XYySHNMJ
{code}
Then i can make an http request like this with curl even:
{code}
curl -H "authorization: Negotiate YIILJAYGKwYBBQ...tzbIo5FHxr30XYySHNMJ"
http://myhost:81/100000.html
{code}
How does this have anything to do with HTTP client? I'm not making that
connection.
> 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]
