Ungrouping the SMART Backend Services tests so that SMART Backend Services Authorization tests can be run without Discovery tests (to reflect that use of the well-known endpoint/discovery tests is a MAY, not a SHALL)
Checking the discovery metadata contents for all of the recommended fields. Though inclusion of all of these fields is a SHOULD, the (optional) metadata contents test requires a correct token_endpoint entry to pass. This is for two reasons:
The token_endpoint value is used in downstream tests
Summary
Fixes #23
This PR fixes the issue in which the Bulk Data V1 SMART Backend Services tests were using Discovery Tests for SMART STU2. V1 Discovery Tests have been updated to reflect the requirements in the Bulk Data V1 SMART Backend Services Authorization profile, including:
token_endpoint
entry to pass. This is for two reasons:token_endpoint
value is used in downstream teststoken_endpoint
value is the only one listed in the Bulk Data V1 IG that is also required in the SMART App Launch STU1 discovery/capabilities.All other recommended fields tested issue warnings rather than failing the tests.
Bulk Data V2 tests are unchanged.
Testing Guidance
Tests can be run locally - select the Bulk Data Access V1.0.1 suite and use the Inferno Reference server preset. Spec test included for the new test.