Sha256: 8bd0e53a7db3d08ab5ac530aae0ebcc3011c9630e699894b25bf0668dd144a00
Contents?: true
Size: 1.76 KB
Versions: 7
Compression:
Stored size: 1.76 KB
Contents
require_relative 'app_redirect_test_stu2' require_relative 'standalone_launch_group' module SMARTAppLaunch class StandaloneLaunchGroupSTU2 < StandaloneLaunchGroup id :smart_standalone_launch_stu2 description %( # Background The [Standalone Launch Sequence](http://hl7.org/fhir/smart-app-launch/STU2/app-launch.html#launch-app-standalone-launch) allows an app, like Inferno, to be launched independent of an existing EHR session. It is one of the two launch methods described in the SMART App Launch Framework alongside EHR Launch. The app will request authorization for the provided scope from the authorization endpoint, ultimately receiving an authorization token which can be used to gain access to resources on the FHIR server. # Test Methodology Inferno will redirect the user to the the authorization endpoint so that they may provide any required credentials and authorize the application. Upon successful authorization, Inferno will exchange the authorization code provided for an access token. For more information on the #{title}: * [Standalone Launch Sequence](http://hl7.org/fhir/smart-app-launch/STU2/app-launch.html#launch-app-standalone-launch) ) config( inputs: { use_pkce: { default: 'true', locked: true }, pkce_code_challenge_method: { default: 'S256', locked: true }, requested_scopes: { default: 'launch/patient openid fhirUser offline_access patient/*.rs' } } ) test from: :smart_app_redirect_stu2 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