Sha256: 988708f2ee3b7b8a3fd868a6b55dddf2085643cbe4800231a7f911e8e97bff4e
Contents?: true
Size: 1.74 KB
Versions: 7
Compression:
Stored size: 1.74 KB
Contents
require_relative 'app_redirect_test_stu2' require_relative 'ehr_launch_group' module SMARTAppLaunch class EHRLaunchGroupSTU2 < EHRLaunchGroup id :smart_ehr_launch_stu2 description %( # Background The [EHR Launch](http://hl7.org/fhir/smart-app-launch/STU2/app-launch.html#launch-app-ehr-launch) is one of two ways in which an app can be launched, the other being Standalone launch. In an EHR launch, the app is launched from an existing EHR session or portal by a redirect to the registered launch URL. The EHR provides the app two parameters: * `iss` - Which contains the FHIR server url * `launch` - An identifier needed for authorization # Test Methodology Inferno will wait for the EHR server redirect upon execution. When the redirect is received Inferno will check for the presence of the `iss` and `launch` parameters. The security of the authorization endpoint is then checked and authorization is attempted using the provided `launch` identifier. For more information on the #{title} see: * [SMART EHR Launch Sequence](http://hl7.org/fhir/smart-app-launch/STU2/app-launch.html#launch-app-ehr-launch) ) config( inputs: { use_pkce: { default: 'true', locked: true }, pkce_code_challenge_method: { default: 'S256', locked: true }, requested_scopes: { default: 'launch openid fhirUser offline_access user/*.rs' } } ) test from: :smart_app_redirect_stu2 do input :launch end redirect_index = children.find_index { |child| child.id.to_s.end_with? 'app_redirect' } children[redirect_index] = children.pop end end
Version data entries
7 entries across 7 versions & 1 rubygems