2015May core #1273 - Only support POST for FHIR RESTful Search

XMLWordPrintableJSON

    • Type: Change Request
    • Resolution: Not Persuasive with Modification
    • Priority: Medium
    • FHIR Core (FHIR)
    • DSTU1 [deprecated]
    • Implementable Technology Specifications
    • Search
    • 2.1.1.2
    • Hide

      Security WG Proposed Resolution:

      GET queries are useful but the concern is worthy of identification as a security risk to be managed by implementors as necessary.

      Need to add text Security.html communications section: The SSL/TLS communications are established prior to any HTTP command/response; so the whole FHIR interaction is protected by the SSL/TLS communications. The security of the endpoints of the SSL/TLS communications must be risk-managed, so as to prevent inappropriate risks (e.g. audit logging of the GET parameters into an unprotected audit log).

      Need to add to Search.html introduction section: Search using GET may include sensitive information in the search parameters therefore secure communications and endpoint management are recommended, see 2.13.0.1

      Show
      Security WG Proposed Resolution: GET queries are useful but the concern is worthy of identification as a security risk to be managed by implementors as necessary. Need to add text Security.html communications section: The SSL/TLS communications are established prior to any HTTP command/response; so the whole FHIR interaction is protected by the SSL/TLS communications. The security of the endpoints of the SSL/TLS communications must be risk-managed, so as to prevent inappropriate risks (e.g. audit logging of the GET parameters into an unprotected audit log). Need to add to Search.html introduction section: Search using GET may include sensitive information in the search parameters therefore secure communications and endpoint management are recommended, see 2.13.0.1
    • Josh Mandel / Michael Donnelly: 13-0-0
    • Enhancement
    • Non-substantive
    • DSTU1 [deprecated]

      Existing Wording: In the simplest case, a search is executed by performing a GET operation in the RESTful framework: GET [base]/[resourcetype]?name=value&… For this RESTful search (see definition in RESTful API), the parameters are a series of name=[value] pairs encoded in the URL or as an application/x-www-form-urlencoded submission for a POST.

      Proposed Wording: In the simplest case, a search is executed by performing a POST operation in the RESTful framework: POST [base]/[resourcetype] For this RESTful search (see definition in RESTful API), the parameters are a series of name=[value] pairs encoded as an application/x-www-form-urlencoded submission for a POST.

      Comment:

      Only POST should be supported on searches. Due to the types of data that may be exposed in querystrings, FHIR should restrict both clients and servers to support x-form-urlencoded POSTs.

            Assignee:
            Unassigned
            Reporter:
            seanmoore
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: