[DOCS-13060] KMIP documentation should say what to do with KMIP keys once they are generated. Created: 26/Sep/19 Updated: 30/Oct/23 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | manual, Server |
| Affects Version/s: | None |
| Fix Version/s: | Server_Docs_20231030 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Mark Brinsmead | Assignee: | Unassigned |
| Resolution: | Won't Do | Votes: | 0 |
| Labels: | docs-security | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Participants: | |
| Days since reply: | 1 year, 14 weeks, 2 days ago |
| Epic Link: | DOCSP-1769 |
| Story Points: | 3 |
| Description |
DescriptionThe docs at ... https://docs.mongodb.com/manual/tutorial/configure-encryption/#encrypt-using-a-new-key ... describe how to generate a new Key identifier with KMIP, but don't say what do to with it when done. In fact, not action seems to be needed, but the next section in the document describes how to start with an existing key, and this confuses users (and TSEs). Perhaps we should explicitly state that `mongod` will save the key that is generated, and no further action is needed.
Scope of changesImpact to Other DocsMVP (Work and Date)Resources (Scope or Design Docs, Invision, etc.) |
| Comments |
| Comment by Education Bot [ 31/Oct/22 ] |
|
Hello! This ticket has been closed due to inactivity. If you believe this ticket is still important, please reopen it and leave a comment to explain why. Thank you! |