protected static class PlainTextAuthProviderBase.PlainTextAuthenticator extends BaseDseAuthenticator
| Modifier | Constructor and Description |
|---|---|
protected |
PlainTextAuthenticator(PlainTextAuthProviderBase.Credentials credentials)
Deprecated.
Preserved for backward compatibility, implementors should use the 3-arg
constructor
PlainTextAuthenticator(Credentials, EndPoint, String) instead. |
protected |
PlainTextAuthenticator(PlainTextAuthProviderBase.Credentials credentials,
EndPoint endPoint,
String serverAuthenticator) |
| Modifier and Type | Method and Description |
|---|---|
ByteBuffer |
evaluateChallengeSync(ByteBuffer challenge)
Evaluate a challenge received from the server.
|
ByteBuffer |
getInitialServerChallenge()
Return a byte buffer containing the expected successful server challenge.
|
ByteBuffer |
getMechanism()
Return a byte buffer containing the required SASL mechanism.
|
initialResponseSync, onAuthenticationSuccessSyncclone, equals, finalize, getClass, hashCode, notify, notifyAll, toString, wait, wait, waitevaluateChallenge, initialResponse, onAuthenticationSuccessprotected PlainTextAuthenticator(@NonNull
PlainTextAuthProviderBase.Credentials credentials,
@NonNull
EndPoint endPoint,
@NonNull
String serverAuthenticator)
@Deprecated protected PlainTextAuthenticator(@NonNull PlainTextAuthProviderBase.Credentials credentials)
PlainTextAuthenticator(Credentials, EndPoint, String) instead.@NonNull public ByteBuffer getMechanism()
BaseDseAuthenticatorThis should be one of:
getMechanism in class BaseDseAuthenticator@NonNull public ByteBuffer getInitialServerChallenge()
BaseDseAuthenticatorThis should be one of:
getInitialServerChallenge in class BaseDseAuthenticator@Nullable public ByteBuffer evaluateChallengeSync(@Nullable ByteBuffer challenge)
SyncAuthenticatorSyncAuthenticator.evaluateChallenge(ByteBuffer) calls this and wraps the result in an immediately
completed future.
challenge - the server's SASL challenge; may be null.null to indicate the client requires no
further action). Note that, if the returned byte buffer is writable, the driver will
clear its contents immediately after use (to avoid keeping sensitive information in
memory); do not reuse the same buffer across multiple invocations. Alternatively, if the
contents are not sensitive, you can make the buffer read-only and safely reuse it.Copyright © 2017–2025. All rights reserved.