Dennis Heimbigner d...@unidata.ucar.edu wrote:
You might create an object, though, that is both credentials provider
and
auth cache.
This is probably the only solution.
But my example still stands, I think.
A credentials providers serves up and caches
a set of credentials.
During the lifetime
On Thu, 2014-01-16 at 13:21 -0700, Dennis Heimbigner wrote:
As I understand it, in httpclient 4,
each credentials provider is solely responsible
for caching of credentials.
Actually it is AuthCache [1].
The question I have is: when authentication
fails using a set of credentials provided
Oleg Kalnichevski wrote:
On Thu, 2014-01-16 at 13:21 -0700, Dennis Heimbigner wrote:
As I understand it, in httpclient 4,
each credentials provider is solely responsible
for caching of credentials.
Actually it is AuthCache [1].
That does not seem correct to me. I looked
at AuthCache
On Thu, 2014-01-16 at 15:16 -0700, Dennis Heimbigner wrote:
Oleg Kalnichevski wrote:
On Thu, 2014-01-16 at 13:21 -0700, Dennis Heimbigner wrote:
As I understand it, in httpclient 4,
each credentials provider is solely responsible
for caching of credentials.
Actually it is
You might create an object, though, that is both credentials provider and
auth cache.
This is probably the only solution.
But my example still stands, I think.
A credentials providers serves up and caches
a set of credentials.
During the lifetime of that provider, the credentials
become out of
