[
https://issues.apache.org/jira/browse/HTTPCLIENT-2402?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Istvan Toth updated HTTPCLIENT-2402:
------------------------------------
Description:
There are two aspect to these changes:
- replacing Subject.doAs() with Subject.callAs()
- handling the changed thread semantics, where the Current Subject is nonger
propagated to new Threads.
The first change is handled by SubjectUtil present in HTTPCLIENT-2358.
The Subject propagation issue breaks SPNEGO authentication for the Async
client, as the Subject is no longer propagated to the execur threads for the
Async operations.
was:
There are two aspect to these changes:
- replacing Subject.doAs() with Subject.callAs()
- handling the changed thread semantics, where the Current Subject is nonger
propagated to new Threads.
The first change is handled by SubjectUtil present in HTTPCLIENT-2358.
The Subject propagation issue is not really a problem, as HttpClient is already
unable to use the Subject directly.
This has probably worked with
> Handle SecurityManager removal
> ------------------------------
>
> Key: HTTPCLIENT-2402
> URL: https://issues.apache.org/jira/browse/HTTPCLIENT-2402
> Project: HttpComponents HttpClient
> Issue Type: Bug
> Reporter: Istvan Toth
> Priority: Major
>
> There are two aspect to these changes:
> - replacing Subject.doAs() with Subject.callAs()
> - handling the changed thread semantics, where the Current Subject is nonger
> propagated to new Threads.
> The first change is handled by SubjectUtil present in HTTPCLIENT-2358.
> The Subject propagation issue breaks SPNEGO authentication for the Async
> client, as the Subject is no longer propagated to the execur threads for the
> Async operations.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
