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
For Gerrit Dashboard: MB-61174 | ||||||
---|---|---|---|---|---|---|
# | Subject | Branch | Project | Status | CR | V |
207362,4 | MB-61174: Don't use 10 iteration counts for unknown users | trinity | kv_engine | Status: MERGED | +2 | +1 |
208067,1 | Merge commit 'couchbase/trinity~2' into trunk | master | kv_engine | Status: ABANDONED | 0 | 0 |
208072,2 | Merge remote-tracking branch 'couchbase/trinity' into trunk | master | kv_engine | Status: MERGED | +2 | +1 |