onc_certification_g10_test_kit 5.4.1 → 6.0.0

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 4c77229c3c6fcbdc7b64a8a0546e9e702d14e043f3f7df0942ebebcda98cc925
-  data.tar.gz: cb085ca88b895bb9a543d13f99fa26afd60cb40a8a99744440e86ba410d4519b
+  metadata.gz: 136ce0bc24a1319f569cc5c8e5a093588bd3a04e069f5cfffa399b1813c2e2b7
+  data.tar.gz: a11f128cfeebb624c5f6e83a3a9205a63c2024859469b0bb6d50fdc6976ee5a9
 SHA512:
-  metadata.gz: b499a93ec58df40a69178e3d78794573c374f3c000f97c78564032fa846e380bbd42cbe0c78ba733e64f6bf2d64c965e99e48deb7783aea1cda6921d11ae2d46
-  data.tar.gz: ad0974f9b1a8f2771b9f30fd4670cf8b391b7201e2466f804a0a10fe54d0f6d599a5d608914f90fe141853ef1628dfb1fc8e39cb1451f6552f4ce86a4a034a48
+  metadata.gz: 74a918854bc39c5094a44769a47cc8ae9695547ed390733103b1e23ba295db8a1aa3abbc75e5c59a26f5aa600e170333a783c6307958e763bda8e6a8dadf9b2c
+  data.tar.gz: 4bd7fc32a080563eb0710de0e91b38b7b76826b01bffc0c9ad0939991644bc3c647fedbd43fb6c831536d4d2fbbae37ac65da11ba12cec0fa9adbbcb0aaeeaad

data/lib/onc_certification_g10_test_kit/base_token_refresh_stu2_group.rb

@@ -0,0 +1,49 @@
+require_relative 'smart_invalid_token_refresh_test'
+
+module ONCCertificationG10TestKit
+  class BaseTokenRefreshSTU2Group < Inferno::TestGroup
+    title 'Token Refresh'
+    description %(
+      # Background
+
+      The #{title} Sequence tests the ability of the system to successfuly
+      exchange a refresh token for an access token. Refresh tokens are typically
+      longer lived than access tokens and allow client applications to obtain a
+      new access token Refresh tokens themselves cannot provide access to
+      resources on the server.
+
+      Token refreshes are accomplished through a `POST` request to the token
+      exchange endpoint as described in the SMART App Launch Framework.
+
+      # Test Methodology
+
+      This test attempts to exchange the refresh token for a new access token
+      and verify that the information returned contains the required fields and
+      uses the proper headers.
+
+      For more information see:
+
+      * [The OAuth 2.0 Authorization
+        Framework](https://tools.ietf.org/html/rfc6749)
+      * [Using a refresh token to obtain a new access token
+        (STU2)](http://hl7.org/fhir/smart-app-launch/STU2/app-launch.html#refresh-access-token)
+    )
+    id :g10_token_refresh_stu2
+
+    test from: :smart_token_refresh_stu2,
+         id: :g10_token_refresh_without_scopes,
+         config: {
+           options: { include_scopes: false }
+         }
+    test from: :smart_token_refresh_body,
+         id: :g10_token_refresh_body_without_scopes
+    test from: :smart_token_refresh,
+         title: 'Server successfully refreshes the access token when optional scope parameter provided',
+         id: :g10_token_refresh_with_scopes,
+         config: {
+           options: { include_scopes: true }
+         }
+    test from: :smart_token_refresh_body,
+         id: :g10_token_refresh_body_with_scopes
+  end
+end

data/lib/onc_certification_g10_test_kit/multi_patient_api_stu1.rb

@@ -21,20 +21,25 @@ module ONCCertificationG10TestKit
     )
 
     description %(
-      Demonstrate the ability to export clinical data for multiple patients in a
-      group using [FHIR Bulk Data Access
-      IG](http://hl7.org/fhir/uv/bulkdata/STU1.0.1/). This test uses [Backend
-      Services
+      This scenario verifies the ability of the system to export clinical data
+      for multiple patients in a group using [FHIR Bulk Data Access
+      IG](http://hl7.org/fhir/uv/bulkdata/STU1.0.1/). This scenario uses
+      [Backend Services
       Authorization](http://hl7.org/fhir/uv/bulkdata/STU1.0.1/authorization/index.html)
       to obtain an access token from the server. After authorization, a group
-      level bulk data export request is initialized. Finally, this test reads
-      exported NDJSON files from the server and validates the resources in each
-      file. To run the test successfully, the selected group export is required
-      to have resources conforming to every profile mapped to [USCDI data
+      level bulk data export request is initialized. Finally, this scenario
+      reads exported NDJSON files from the server and validates the resources in
+      each file. To run the test successfully, the selected group export is
+      required to have resources conforming to every profile mapped to [USCDI
+      data
       elements](https://www.healthit.gov/isa/us-core-data-interoperability-uscdi).
       Additionally, it is expected the server will provide Encounter, Location,
       Organization, and Practitioner resources as they are referenced as must
       support elements in required resources.
+
+      Prior to executing this scenario, register Inferno with the following JWK Set Url:
+
+      * `#{Inferno::Application[:base_url]}/custom/g10_certification/.well-known/jwks.json`
     )
     id :multi_patient_api
     run_as_group

data/lib/onc_certification_g10_test_kit/multi_patient_api_stu2.rb

@@ -21,20 +21,25 @@ module ONCCertificationG10TestKit
     )
 
     description %(
-      Demonstrate the ability to export clinical data for multiple patients in a
-      group using [FHIR Bulk Data Access
-      IG](https://hl7.org/fhir/uv/bulkdata/STU2/). This test uses [Backend
+      This scenario verifies the ability of the system to export clinical data
+      for multiple patients in a group using [FHIR Bulk Data Access
+      IG](https://hl7.org/fhir/uv/bulkdata/STU2/). This scenario uses [Backend
       Services
       Authorization](http://www.hl7.org/fhir/smart-app-launch/backend-services.html)
       to obtain an access token from the server. After authorization, a group
-      level bulk data export request is initialized. Finally, this test reads
-      exported NDJSON files from the server and validates the resources in each
-      file. To run the test successfully, the selected group export is required
-      to have resources conforming to every profile mapped to [USCDI data
+      level bulk data export request is initialized. Finally, this scenario
+      reads exported NDJSON files from the server and validates the resources in
+      each file. To run the test successfully, the selected group export is
+      required to have resources conforming to every profile mapped to [USCDI
+      data
       elements](https://www.healthit.gov/isa/us-core-data-interoperability-uscdi).
       Additionally, it is expected the server will provide Encounter, Location,
       Organization, and Practitioner resources as they are referenced as must
       support elements in required resources.
+
+      Prior to executing this scenario, register Inferno with the following JWK Set Url:
+
+      * `#{Inferno::Application[:base_url]}/custom/g10_certification/.well-known/jwks.json`
     )
     id :multi_patient_api_stu2
     run_as_group