[DOCS-13461] [Compass] Compass does not require a password for Kerberos authenticated connection but doc says required Created: 26/Feb/20 Updated: 30/Oct/23 Resolved: 02/Mar/20 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | Compass |
| Affects Version/s: | None |
| Fix Version/s: | Server_Docs_20231030 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Felicia Hsieh | Assignee: | Tahiya Chowdhury (Inactive) |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Participants: | |
| Days since reply: | 3 years, 49 weeks, 5 days ago |
| Story Points: | 1 |
| Description |
it DescriptionWebsite: https://docs.mongodb.com/compass/current/connect/ > "Fill in Individual Fields" tab > "Kerberos" tab Password field should be blank if connecting to Compass with Kerberos authentication. This fix was in Compass 1.16 per https://support.mongodb.com/case/00525365 so customers will provide a password when perhaps they should not. There are about 5 SFSC cases and a HELP ticket. Post Compass version 1.16.x and later it is best NOT to provide the password. Docs say, "Select Kerberos if the deployment uses Kerberos as its authentication mechanism. If selected, you must provide the Principal, *Password*, and Service Name to authenticate the user." There is no mention of this change in Compass Release Notes. It would help reduce SFSC Compass tickets if website text can be updated.
Scope of changesImpact to Other DocsMVP (Work and Date)Resources (Scope or Design Docs, Invision, etc.) |
| Comments |
| Comment by Tahiya Chowdhury (Inactive) [ 28/Feb/20 ] |
| Comment by Tahiya Chowdhury (Inactive) [ 28/Feb/20 ] |
| Comment by Tahiya Chowdhury (Inactive) [ 28/Feb/20 ] |