Sha256: 15a5c12c7ff1b663a83f278ac8672cfb3dab4bb23fd6016b2a36be687af2b3f7

Contents?: true

Size: 1.43 KB

Versions: 1

Compression:

Stored size: 1.43 KB

Contents

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
        }
      }
    )
  end
end

Version data entries

1 entries across 1 versions & 1 rubygems

Version Path
smart_app_launch_test_kit-0.1.4 lib/smart_app_launch/standalone_launch_group_stu2.rb