[SERVER-48910] Do not consider keystore.metadata as a keystore on <= 4.0 Created: 17/Jun/20  Updated: 29/Oct/23  Resolved: 26/Mar/21

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: 4.0.24

Type: Question Priority: Major - P3
Reporter: Sara Golemon Assignee: Sara Golemon
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Backports
Related
Backwards Compatibility: Fully Compatible
Backport Requested:
v3.6
Sprint: Security 2021-04-05
Participants:

 Description   

On ESE startup, we determine the KMIP key identifier by looping through any keystores looking for the first keyname. This assumption made sense prior to adopting the v1 page layout.  Now that we have the metadata store, the keyidentifiers are more variable.  We should backport the exception used in v4.2 and later to ignore keystore.metadata in this loop.

 



 Comments   
Comment by Githook User [ 26/Mar/21 ]

Author:

{'name': 'Sara Golemon', 'email': 'sara.golemon@mongodb.com', 'username': 'sgolemon'}

Message: SERVER-48910 Do not consider keystore.metadata when searching for ESE keys

This is a very small fractional backport of SERVER-39944
containing just the metadata.keystore filename exception.
Branch: v4.0
https://github.com/10gen/mongo-enterprise-modules/commit/0fa6b06de0d2d404d86b9979134fea0954b23c3c

Generated at Thu Feb 08 05:18:24 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.