Retrieving encryption schema should include tenancy

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Won't Do
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • Service Arch
    • ALL
    • 1
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None

      Today we strip the tenantId information when we access the schema containing the encryption information.

      We should confirm and make the change to include the tenantId here.

      We should also update the jstest related to FLE to use an unsigned security token and prefixed db in order to simulated AP's behavior.

            Assignee:
            [DO NOT USE] Backlog - Service Architecture
            Reporter:
            Mathis Bessa (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated:
              Resolved: