Details
-
Bug
-
Resolution: Fixed
-
Critical
-
7.6.0
-
Triaged
-
0
-
Yes
-
March-June 24
Description
I have an application which uses SCRAM SHA 512 for SASL AUTH and is sending invalid credentials.
Against server 7.1 I see that the server responds with SASL CONTINUE and the SASL STEP then fails with an error from the server.
Against server 7.6 I see that the server responds with SASL CONTINUE but with an invalid iterator value that my scram library is rejecting.
Is this change intentional? I've attached 2 packets caps illustrating this.
Attachments
Issue Links
- relates to
-
GOCBC-1615 connecting to CBS 7.6 with non TLS bad credentials doesn't return ErrAuthenticationFailure
- Closed