Incorrect exceptions thrown when for auth issues

Discovered some inconsistencies in Java exception handling when debugging server-side password changes:

• For a KV operation : At connection time they are no validation of login password but only when a “real operation is done” like collection.insert or bucket.waitUntilReady
  in this case a generic exception is throw UnambiguousTimeoutException or AmbiguousTimeoutException
  an event of type SaslAuthenticationFailedEvent is generated inside the event bus
• For a N1QL operation : when the password change a basic CouchbaseException is thrown

Could we fix/add a consistent auth failure exception across the different services and be able to detect it as early as possible?