Class | Description | |
---|---|---|
BasicChallengeHandler |
Challenge handler for Basic authentication as defined in RFC 2617.
This BasicChallengeHandler can be loaded and instantiated using In addition, one can install general and realm-specific The following example loads an instance of a |
|
ChallengeHandler | A ChallengeHandler is responsible for producing responses to HTTP 401 authentication challenges. | |
ChallengeHandlers |
Responsible for both loading fresh ChallengeHandler instances
and managing a concept of a default challenge handler. |
|
ChallengeRequest | An immutable object representing the challenge presented by the server when the client accessed the URI represented by a location. | |
ChallengeResponse | A challenge response contains a byte array representing the response to the server, and a reference to the next challenge handler to handle any further challenges for the request. | |
ChallengeResponseFuture | Future-based support for asynchronous functions returning a value. | |
DispatchChallengeHandler |
A DispatchChallengeHandler is responsible for dispatching challenge requests
to appropriate challenge handlers when challenges
arrive from specific URI locations in HTTP 401 responses. |
|
KerberosChallengeHandler |
A KerberosChallengeHandler , when registered with the DispatchChallengeHandler
can be used to directly respond to "Negotiate" challenges where Kerberos-generated authentication
credentials are required. |
|
LoginHandler | A login handler is responsible for obtaining credentials from an arbitrary source. | |
NegotiableChallengeHandler |
A NegotiableChallengeHandler can be used to directly respond to
"Negotiate" challenges, and in addition, can be used indirectly in conjunction
with a NegotiateChallengeHandler
to assist in the construction of a challenge response using object identifiers. |
|
NegotiateChallengeHandler | A Negotiate Challenge Handler handles initial empty "Negotiate" challenges from the server. |