Feature #7451
Updated by Rob Nahf over 8 years ago
Current libclient_java doesn't support the use of multiple auth tokens via D1Client, as it somewhat does with certificates. That is to say, the header can be added, but it will affect all other clients using the D1Client multipartRestClient.
I propose to add an AuthTokenSession class that can be passed into the Session parameter for API calls.
The AuthTokenSession will not use certificates, so will require I different way to set up the connectionManager for the httpClient. Do we still need to have host verification?
The session passed into the API should know how to switch to using the attached HttpClient
Using a request interceptor to set the Authorization header to prevent it from being messed with by other headers.
I propose to add an AuthTokenSession class that can be passed into the Session parameter for API calls.
The AuthTokenSession will not use certificates, so will require I different way to set up the connectionManager for the httpClient. Do we still need to have host verification?
The session passed into the API should know how to switch to using the attached HttpClient
Using a request interceptor to set the Authorization header to prevent it from being messed with by other headers.
