[SERVER-49488] Mongo shell is conflating authentication & network errors Created: 13/Jul/20 Updated: 17/Sep/20 Resolved: 20/Aug/20 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Networking, Shell |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Adinoyi Omuya | Assignee: | Robert Guo (Inactive) |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| Backport Requested: |
v4.4
|
||||||||||||
| Sprint: | STM 2020-08-10, STM 2020-08-24 | ||||||||||||
| Participants: | |||||||||||||
| Story Points: | 1 | ||||||||||||
| Description |
|
The mongo shell attempts to authenticate right after it connects to a server and returns an exception if it's unable to. This means that if the client credentials are invalid, it will interpret that as a connection failure and raise an exception. It is unexpected that the shell would conflate an authentication problem with the general class of network connection failures. Here's what clients see when all that's wrong is invalid credentials:
It's unclear to me if this is expected behavior (it's confusing at best). If so, using a more generic error message instead of specifically offering that clients check their IP allowlist would be less confusing to users. If not, we should fix it. |
| Comments |
| Comment by Githook User [ 17/Sep/20 ] |
|
Author: {'name': 'Robert Guo', 'email': 'robert.guo@10gen.com', 'username': 'guoyr'}Message: (cherry picked from commit e4aa1021d6e126b46f334d3354c97f052e3d4561) |
| Comment by Robert Guo (Inactive) [ 20/Aug/20 ] |
|
Sounds good. Thanks Wisdom! |
| Comment by Adinoyi Omuya [ 20/Aug/20 ] |
|
I think this ticket is still applicable but it is relatively minor so I'm happy if y'all want to close it as "Won't Fix" - especially if it's not an issue in mongosh. |
| Comment by Robert Guo (Inactive) [ 20/Aug/20 ] |
|
adinoyi.omuya Since you mentioned in |
| Comment by Brooke Miller [ 14/Jul/20 ] |
|
Regardless of whether you get the same error message, we will update this message to 'You have failed to connect to an Atlas Cluster.' |