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

Implement getAuthEnvironment for GRPCSession

    XMLWordPrintableJSON

Details

    • Icon: Improvement Improvement
    • Resolution: Fixed
    • Icon: Major - P3 Major - P3
    • 7.3.0-rc0
    • None
    • None
    • Service Arch
    • Fully Compatible
    • Security 2023-12-25
    • 147

    Description

      With the introduction of generic logging in SERVER-71100, the construction and access to RestrictionEnvironment is implemented by each Session in Session::getAuthEnvironment. The previous implementation of RestrictionEnvironment relies on SockAddrs which are used in CommonAsioSession.

      This ticket involves figuring out how GRPCSession can fit into or work around the security related concepts such as RestrictionEnvironment.

      Along with the implementation of Session::getAuthEnvironment, complete the linked TODO found in the enterprise modules by removing the cast to CommonAsioSession. The need for this cast came from the logging restrictions promised by audit logs to be a certain form for customer logging ingestion e.g.

      { ... , local: {ip: '127.0.0.1', port: 27017}, remote: {ip: '::1', port: 12345}, ... } 

      Attachments

        Activity

          People

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

            Dates

              Created:
              Updated:
              Resolved: