Uploaded image for project: 'Documentation'
  1. Documentation
  2. DOCS-12531

Docs for SERVER-39242: Implement parsing for additionalProperties on mongocryptd

    XMLWordPrintable

Details

    • Task
    • Status: Blocked
    • Major - P3
    • Resolution: Unresolved
    • None
    • 4.1.9
    • manual, Server

    Description

      Description

      Description:

      You may not need to document this change independently from the rest of the field-level encryption project, but I'm not totally sure. This change made it possible to use the JSON Schema 'additionalProperties' keyword to indicate that all other not-explicitly-named properties are encrypted. For example, consider the schema {type: "object", properties: {foo:

      Unknown macro: {type}

      , bar:

      Unknown macro: {type}

      , additionalProperties: {encrypt: {}}}. This schema means that field "foo" must be a string (if it exists), field "bar" must be a number (if it exists), and all other fields must be encrypted.

      Engineering Ticket Description:

      The result of parsing additionalProperties should be an edge in the encryption tree which represents the "else" case, meaning take this path if no other edges match the current path component. This ticket should include the schema parsing as well as the tree traversal.

      Scope of changes

      Impact to Other Docs

      MVP (Work and Date)

      Resources (Scope or Design Docs, Invision, etc.)

      Attachments

        Issue Links

          Activity

            People

              ravind.kumar Ravind Kumar (Inactive)
              kay.kim@mongodb.com Kay Kim (Inactive)
              Andrew Feierabend Andrew Feierabend (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                2 years, 22 weeks, 3 days ago