Uploaded image for project: 'FHIR Specification Feedback'
  1. FHIR Specification Feedback
  2. FHIR-38698

Clarify step 1a - 5 - Query mutual TLS Public Cert

    XMLWordPrintableJSON

Details

    • Icon: Change Request Change Request
    • Resolution: Not Persuasive
    • Icon: Medium Medium
    • US Da Vinci PDex (FHIR)
    • current
    • Financial Mgmt
    • Payer-to-Payer Exchange [deprecated]
    • Hide

      The payertopayerexchange.html page has been substantially updated since this ticket was submitted. An additional supplemental guide was also made available in https://github.com/hl7-davinci/pdex-payer-payer to explain the use of mTLS.

      Show
      The payertopayerexchange.html page has been substantially updated since this ticket was submitted. An additional supplemental guide was also made available in https://github.com/hl7-davinci/pdex-payer-payer to explain the use of mTLS.
    • Mark Scrimshire / Rachael Foerster : 10-0-2

    Description

      How does a server exactly 'Query mutual TLS Public Cert work' ?

      When using mutual TLS the server knows the details of the certificate the client used (common name, thumbprint etc.), how are those matched against the endpoint directory?

      How does this work when using proxies or load balancers? Mutual TLS is done at the network edge, so the proxies / load balancers should be doing this query to verify the certificate? . . . but usually they are not under the developer control?

      Attachments

        Activity

          People

            Unassigned Unassigned
            michelemottini Michele Mottini
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: