[SERVER-11635] Bad Error Message for User Not Found in Mongos for GSSAPI on Windows Created: 08/Nov/13  Updated: 08/Nov/13  Resolved: 08/Nov/13

Status: Closed
Project: Core Server
Component/s: Security
Affects Version/s: 2.5.3
Fix Version/s: None

Type: Bug Priority: Trivial - P5
Reporter: Craig Wilson Assignee: Unassigned
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Windows Mongos


Issue Links:
Duplicate
duplicates SERVER-11354 Improve log message when auth'd user ... Closed
Operating System: ALL
Participants:

 Description   

When using GSSAPI against a Windows mongos, the error message for user not found is unhelpful. Note that the user attempting to login must be a valid user in the KDC, just not one that has been added to MongoDB.

2013-11-08T07:47:04.549-0600 Error: 8 invalid parameter: expected an object () at src/mongo/shell/db.js:1199
exception: login failed

The same error message against a mongod looks like this:

2013-11-08T07:47:26.222-0600 Error: 11 User not found at src/mongo/shell/db.js:1199
exception: login failed



 Comments   
Comment by Craig Wilson [ 08/Nov/13 ]

Latest nightly has this fixed already.

Comment by Craig Wilson [ 08/Nov/13 ]

This is not shell specific, but also happens with the .NET driver. This is working off a nightly I pulled yesterday. I'll attempt to install the latest .msi that exists and see if it goes away.

Comment by Spencer Brody (Inactive) [ 08/Nov/13 ]

This looks like a dup of SERVER-11354, which should be fixed in master. Can you confirm that this works on the nightlies?

Comment by Eric Milkie [ 08/Nov/13 ]

Is this specific to the shell? Also, does this problem occur for Linux Kerberos as well?
For triage, I'd like to understand the scope of the issue.

Generated at Thu Feb 08 03:26:21 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.