|
|
UDAP-CI/HL7 UDAP Discovery Test Release 1-0/01-hl7-udap-discovery-happy-path
|
1 |
Happy Path: Retrieve and verify the FHIR Server's UDAP Well-Known
Uniform Resource Identifier JSON document, using test version 1.0.
Test System Details (in order of appearance):
[Origin 1: The Client's RESTful client]
[Destination 1: The Server's OAuth Resource Server (i.e. where UDAP metadata is available at <base>/.well-known/udap, and a FHIR Server at <base> if appropriate)] |
JSON |
1 |
FHIR 4.0.1
|
|
|
UDAP-CI/HL7 UDAP JWT Test Release 1-0/01-hl7-udap-full-workflow-rs256-then-patient-read
|
1 |
Demonstrate the full UDAP workflow: Discovery, Registration,
Authorization, and resource access (using a Patient read),
using the RS256 algorithm for all JWTs.
This scenario is generic and can be used with any grant types.
Test System Details (in order of appearance):
[Origin 1: The Client's RESTful client]
[Destination 1: The Server's OAuth Resource Server (i.e. where UDAP metadata is available at <base>/.well-known/udap, and a RESTful FHIR Server at <base> if appropriate)]
[Destination 2: The Server's UDAP OAuth Authorization Server]
NOTE: This TestScript requires an external client. It will not function correctly if Touchstone is chosen as the client. |
JSON |
8 |
FHIR 4.0.1
|
|
|
UDAP-CI/HL7 UDAP JWT Test Release 1-0/02-hl7-udap-jwt-additional-key-not-used-to-sign---server-sut
|
1 |
Demonstrate UDAP Registration and Token Request where the signing key
of the JWTs sent by the client is in x5c and a different key, not used
to sign the JWT, is identified in another JOSE header field.
This scenario tests the server only, and must be used with a simulated client.
Test System Details (in order of appearance):
[Origin 1: The Client's RESTful client]
[Destination 1: The Server's UDAP OAuth Authorization Server]
NOTE: This TestScript requires an external client. It will not function correctly if Touchstone is chosen as the client. |
JSON |
4 |
FHIR 4.0.1
|
|
|
UDAP-CI/HL7 UDAP Registration Test Release 1-0/01-hl7-udap-registration-full-workflow
|
1 |
Happy Path: Demonstrate the full UDAP Registration
workflow: Discovery and Registration.
This scenario is generic and can be used with any grant types.
Test System Details (in order of appearance):
[Origin 1: The Client's RESTful client]
[Destination 1: The Server's OAuth Resource Server (i.e. where UDAP metadata is available at <base>/.well-known/udap, and a RESTful FHIR Server at <base> if appropriate)]
[Destination 2: The Server's UDAP OAuth Authorization Server]
NOTE: This TestScript requires an external client. It will not function correctly if Touchstone is chosen as the client. |
JSON |
2 |
FHIR 4.0.1
|
|
|
UDAP-CI/HL7 UDAP Registration Test Release 1-0/02-hl7-udap-registration
|
1 |
Happy Path: Demonstrate UDAP Registration.
This scenario is generic and can be used with any grant types.
Test System Details (in order of appearance):
[Origin 1: The Client's RESTful client]
[Destination 1: The Server's UDAP OAuth Authorization Server]
NOTE: This TestScript requires an external client. It will not function correctly if Touchstone is chosen as the client. |
JSON |
1 |
FHIR 4.0.1
|