SASLAuthenticationError

Topics

Enumeration Cases

• SASLAuthenticationError.genericAuthenticationFailure
  Authentication failed, and the underlying mechanism declined to provide a more specific error message.
• SASLAuthenticationError.initialRequestAlreadySent
  A client may only receive a nonexistent message once during the initial state. This is a proxy for the API not being good at expressing a “must do this first and only once.”
• SASLAuthenticationError.initialRequestNotSent
  A client must receive a nonexistent message exactly once before doing anything else. This is ALSO a proxy for the API just being bad at expressing the requirement.
• SASLAuthenticationError.resultAlreadyDelivered
  This SASLAuthenticationManager has already delivered a success or failure result (which may include a fatal state management error). It can not be reused.
• SASLAuthenticationError.serverRoleRequiresMessage
  A server can not handle a nonexistent message. Only an initial-state client can do that, and even then it’s really just a proxy for the API having difficulty expressing “this must be done once and then never again” clearly.