org.apache.http.auth.AuthScheme |
Known Indirect Subclasses |
This interface represents an abstract challenge-response oriented authentication scheme.
An authentication scheme should be able to support the following functions:
Authentication schemes may ignore method name and URI parameters if they are not relevant for the given authentication mechanism
Authentication schemes may be stateful involving a series of challenge-response exchanges
Public Methods | |||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|
Produces an authorization string for the given set of
Credentials . | |||||||||||
Returns authentication parameter with the given name, if available.
| |||||||||||
Returns authentication realm.
| |||||||||||
Returns textual designation of the given authentication scheme.
| |||||||||||
Authentication process may involve a series of challenge-response exchanges.
| |||||||||||
Tests if the authentication scheme is provides authorization on a per
connection basis instead of usual per request basis
| |||||||||||
Processes the given challenge token.
|
Produces an authorization string for the given set of Credentials
.
credentials | The set of credentials to be used for athentication |
---|---|
request | The request being authenticated |
AuthenticationException | if authorization string cannot be generated due to an authentication failure |
---|
Returns authentication parameter with the given name, if available.
name | The name of the parameter to be returned |
---|
Returns authentication realm. If the concept of an authentication
realm is not applicable to the given authentication scheme, returns
null
.
Returns textual designation of the given authentication scheme.
Authentication process may involve a series of challenge-response exchanges. This method tests if the authorization process has been completed, either successfully or unsuccessfully, that is, all the required authorization challenges have been processed in their entirety.
Tests if the authentication scheme is provides authorization on a per connection basis instead of usual per request basis
Processes the given challenge token. Some authentication schemes may involve multiple challenge-response exchanges. Such schemes must be able to maintain the state information when dealing with sequential challenges
header | the challenge header |
---|
MalformedChallengeException |
---|