Sha256: 349f8853bcce7f8ea76fe17715e336a10bba62429ce893915f291297162664ab
Contents?: true
Size: 1.77 KB
Versions: 21
Compression:
Stored size: 1.77 KB
Contents
require_relative 'token_refresh_test'
require_relative 'token_refresh_body_test'
require_relative 'token_response_headers_test'
module SMARTAppLaunch
class TokenRefreshGroup < Inferno::TestGroup
id :smart_token_refresh
title 'SMART Token Refresh'
short_description 'Demonstrate the ability to exchange a refresh token for an access token.'
description %(
# Background
The #{title} Sequence tests the ability of the system to successfully
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](https://www.hl7.org/fhir/smart-app-launch/1.0.0/index.html#step-5-later-app-uses-a-refresh-token-to-obtain-a-new-access-token).
# 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](https://www.hl7.org/fhir/smart-app-launch/1.0.0/index.html#step-5-later-app-uses-a-refresh-token-to-obtain-a-new-access-token)
)
test from: :smart_token_refresh
test from: :smart_token_refresh_body
test from: :smart_token_response_headers,
config: {
requests: {
token: { name: :token_refresh }
}
}
end
end
Version data entries
21 entries across 21 versions & 1 rubygems