Asymmetric Client refresh token tests - inconsistencies between 9.12.3.01 and 9.12.3.03

[jwjahns]

Hello,

Test 9.12.3 (Token Refresh for asymmetric clients launch) appears to be mixing SMART STU2 and STU1 code.
Test 9.12.3.01 pulls from test smart_token_refresh_stu2:

onc-certification-g10-test-kit/lib/onc_certification_g10_test_kit/base_token_refresh_stu2_group.rb

Lines 33 to 34 in 64bbabe

	test from: :smart_token_refresh_stu2,
	id: :g10_token_refresh_without_scopes,

But test 9.12.3.03 pulls from test smart_token_refresh:

onc-certification-g10-test-kit/lib/onc_certification_g10_test_kit/base_token_refresh_stu2_group.rb

Lines 40 to 42 in 64bbabe

	test from: :smart_token_refresh,
	title: 'Server successfully refreshes the access token when optional scope parameter provided',
	id: :g10_token_refresh_with_scopes,

The result is a different refresh token request between these two tests. You can see this using the reference server, e.g.:
https://inferno.healthit.gov/suites/g10_certification/gVKFKnQsmfl#g10_certification-Group06-g10_asymmetric_launch

In the above test run, Test 9.12.3.01 includes a client_assertion in the Request Body. Test 9.12.3.03 does not. I think this is due to the above code discrepancy.

[Jammjammjamm]

You are correct, thank you for reporting this. We will fix this ASAP.

[Jammjammjamm]

We released version 6.0.1 yesterday which should address this issue.