Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-48910

Do not consider keystore.metadata as a keystore on <= 4.0

    XMLWordPrintable

Details

    • Question
    • Status: Closed
    • Major - P3
    • Resolution: Fixed
    • None
    • 4.0.24
    • None
    • None
    • Fully Compatible
    • v3.6
    • Security 2021-04-05

    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.

       

      Attachments

        Activity

          People

            sara.golemon@mongodb.com Sara Golemon
            sara.golemon@mongodb.com Sara Golemon
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: