Sha256: 43b9a7cb2e20923917038bc9bda17341396c8ab6454fd5ca6760f8dddc47bf80
Contents?: true
Size: 1.83 KB
Versions: 2
Compression:
Stored size: 1.83 KB
Contents
require_relative 'token_response_body_test_stu2_2' require_relative 'standalone_launch_group_stu2' module SMARTAppLaunch class StandaloneLaunchGroupSTU22 < StandaloneLaunchGroupSTU2 id :smart_standalone_launch_stu2_2 description %( # Background The [Standalone Launch Sequence](http://hl7.org/fhir/smart-app-launch/STU2.2/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.2/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_token_response_body_stu2_2 token_response_body_index = children.find_index { |child| child.id.to_s.end_with? 'token_response_body' } children[token_response_body_index] = children.pop end end
Version data entries
2 entries across 2 versions & 1 rubygems
Version | Path |
---|---|
smart_app_launch_test_kit-0.4.5 | lib/smart_app_launch/standalone_launch_group_stu2_2.rb |
smart_app_launch_test_kit-0.4.4 | lib/smart_app_launch/standalone_launch_group_stu2_2.rb |