|
||||||||||
| PREV NEXT | FRAMES NO FRAMES | |||||||||
| Packages that use ReplayCache | |
|---|---|
| org.apache.directory.server.kerberos.shared | |
| org.apache.directory.server.kerberos.shared.replay | Provides the interface and in-memory implementation of a Kerberos replay cache. |
| Uses of ReplayCache in org.apache.directory.server.kerberos.shared |
|---|
| Methods in org.apache.directory.server.kerberos.shared with parameters of type ReplayCache | |
|---|---|
static Authenticator |
KerberosUtils.verifyAuthHeader(ApplicationRequest authHeader,
Ticket ticket,
EncryptionKey serverKey,
long clockSkew,
ReplayCache replayCache,
boolean emptyAddressesAllowed,
java.net.InetAddress clientAddress,
CipherTextHandler lockBox,
KeyUsage authenticatorKeyUsage,
boolean isValidate)
Verifies an AuthHeader using guidelines from RFC 1510 section A.10., "KRB_AP_REQ verification." |
| Uses of ReplayCache in org.apache.directory.server.kerberos.shared.replay |
|---|
| Classes in org.apache.directory.server.kerberos.shared.replay that implement ReplayCache | |
|---|---|
class |
InMemoryReplayCache
"The replay cache will store at least the server name, along with the client name, time, and microsecond fields from the recently-seen authenticators, and if a matching tuple is found, the KRB_AP_ERR_REPEAT error is returned." We will store the entries using an HashMap which key will be the client principal, and we will store a list of entries for each client principal. |
|
||||||||||
| PREV NEXT | FRAMES NO FRAMES | |||||||||