[DOCS-15999] Investigate changes in SERVER-74999: Create configuration file option for custom X.509 extension for cluster membership Created: 01/Apr/23  Updated: 13/Nov/23  Resolved: 29/Jun/23

Status: Closed
Project: Documentation
Component/s: manual, Server
Affects Version/s: None
Fix Version/s: 7.0.0-rc0, Server_Docs_20231030, Server_Docs_20231106, Server_Docs_20231105, Server_Docs_20231113

Type: Task Priority: Major - P3
Reporter: Backlog - Core Eng Program Management Team Assignee: Kenneth Dyer
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Documented
documents SERVER-74999 Create configuration file option for ... Closed
Participants:
Days since reply: 31 weeks, 6 days ago

 Description   
Original Downstream Change Summary

This change adds a new mechanism by which cluster members may identify each other whilst using X.509 based authentication.

Description of Linked Ticket

Define an X.509 extension that should explicitly be set on certificates when the clusterMembershipExtension configuration option is specified. All connecting clients that provide a certificate with that extension set to the value of clusterMembershipExtension will be treated as peer servers provided that the host server is configured to handle X.509 auth.



 Comments   
Comment by Kenneth Dyer [ 29/Jun/23 ]

DOCSP-28315

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