[
https://issues.apache.org/jira/browse/HTTPCLIENT-1582?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16504801#comment-16504801
]
Roland Young commented on HTTPCLIENT-1582:
------------------------------------------
If the JNA issue referred to is addressed as requested by the comment I have
just posted in their GitHub project, no action is needed in this project.
Otherwise, there are two possible approaches
# Use code similar to [this
patch|https://github.com/Waffle/waffle/commit/ebedaf7e92535e2cdcbd46bf9032ebce360383ed]
to Waffle
# Define a hard-coded constant WindowsNegotiateScheme#MAX_TOKEN_SIZE as 49152
(48k), to correspond to the maximum size of a token that can be passed in an
HTTP header.
I intend to test at least one of these as a workaround to an issue we are
facing with our product (which uses HttpClient to make a headless connection to
our SSO service), so I may be able to contribute a patch.
> SSPI-based auth might fail if output token size is too small
> ------------------------------------------------------------
>
> Key: HTTPCLIENT-1582
> URL: https://issues.apache.org/jira/browse/HTTPCLIENT-1582
> Project: HttpComponents HttpClient
> Issue Type: Bug
> Components: HttpClient (classic)
> Affects Versions: 4.4 Beta1
> Reporter: Michael Osipov
> Priority: Major
> Labels: stuck, volunteers-wanted
> Fix For: Stuck
>
>
> It might happen that a user has many groups, this makes the output token
> bigger. It might exceed the limit defined by JNA. Refer to JNA's issue
> [261|https://github.com/twall/jna/issues/261].
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
