[SERVER-50538] Rare auth counter behavior is not taken into account by certain tests that use them Created: 25/Aug/20 Updated: 29/Oct/23 Resolved: 09/Feb/21 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 4.9.0 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Adam Cooper (Inactive) | Assignee: | Spencer Jackson |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||
| Operating System: | ALL | ||||||||
| Backport Requested: |
v4.4
|
||||||||
| Sprint: | Security 2020-10-05, Security 2020-12-28, Security 2021-01-25, Security 2021-02-08, Security 2021-02-22 | ||||||||
| Participants: | |||||||||
| Linked BF Score: | 35 | ||||||||
| Description |
|
If the server receives an auth request that uses saslStart and requires a saslContinue, but never runs saslContinue, then the server will count a received authentication, but not a successful one. There is at least one test that assumes this will never happen, and uses an equal number of received authentication attempts and successful authentication attempts as a metric for correctness. This/these test(s) should take this behavior into account. Per sara.golemon: > The right solution may be grabbing the auth stats right after rst.awaitSecondaryNodes(); and verify that speculative, cluster and total auths are all >= ($numberOfNodes - 1). Then trigger all host-connections to re-establish, and get mech stats, then make sure received and successful both went up (and by equal amounts). |
| Comments |
| Comment by Githook User [ 09/Feb/21 ] |
|
Author: {'name': 'Spencer Jackson', 'email': 'spencer.jackson@mongodb.com', 'username': 'spencerjackson'}Message: |
| Comment by Spencer Jackson [ 22/Jan/21 ] |
|
CR: https://mongodbcr.appspot.com/725770011/ |