[DOCS-9000] Kerberos Authentication on Windows from mongo client only works with FQDN Created: 28/Sep/16 Updated: 13/Nov/23 Resolved: 15/Jun/18 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | Server |
| Affects Version/s: | None |
| Fix Version/s: | 3.2.0-rc0, Server_Docs_20231030, Server_Docs_20231106, Server_Docs_20231105, Server_Docs_20231113 |
| Type: | Task | Priority: | Minor - P4 |
| Reporter: | Emily Hall | Assignee: | Anthony Sansone (Inactive) |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Participants: | |||||||||
| Days since reply: | 5 years, 34 weeks, 6 days ago | ||||||||
| Description |
|
When authenticating from a Windows 7 2.6.1 enterprise client to a MongoDB 2.4.9 enterprise instance using Kerberos, the connection will only succeed if the FQDN is used in the URL instead of the short host name. Clients on Linux seem unaffected by this problem. Example 1 - Using FQDN in the URL and everything works; C:\Apps\MongoDB\2.6.1\bin>mongo host10601.intranet.mydomain.com:27118/admin - Example 2 - Using short name and get a GSSAPI error; C:\Apps\MongoDB\2.6.1\bin>mongo host10601:27118/admin -authenticationDatabase= Example 3 - DNS lookup of short name showing that FQDN is available; Non-authoritative answer: |
| Comments |
| Comment by Anthony Sansone (Inactive) [ 15/Jun/18 ] |
|
This issue is noted for version 3.6. Both MongoDB 2.4 and 2.6 are at end of life. |