[DOCS-5113] KeyFile valid charset exposition is incomplete Created: 26/Mar/15 Updated: 11/Jan/17 Resolved: 27/Jul/16 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | manual |
| Affects Version/s: | None |
| Fix Version/s: | 01112017-cleanup |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Ian Bentley | Assignee: | Unassigned |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: | |||
| Participants: | |
| Days since reply: | 8 years, 46 weeks, 6 days ago |
| Description |
|
The docs currently read: "A key’s length must be between 6 and 1024 characters and may only contain characters in the base64 set." This can lead to frustration, because mongodb won't handle the '=' character gracefully. '=' is used as a padding character to round out base 64 encodings that don't round to x % 3 chars. Since '=' occurs in most base64 encodings, I believe we should mention that it is an invalid character for keyFiles. |