evernorth / hl7-fhir-udap-client-test-ui Goto Github PK

In touchstone, test scenarios are split between B2B and B2C. When a B2B test is executed, it looks for a specific B2B registration, and subsequently for B2C, it looks for a B2C registration. This can cause issues with the current implementation because we always register both at the same time, and touchstone might inadvertantly fail our implementation because we sent the "wrong" registration first.

This issue/enhancement is to simply have an additional button that allows us to send through the registration that we want (b2b or b2c).

A minor issue discovered during the connectathon 35. In the B2B/client_credentials registration- it doesn't make sense to set a "response_types" value- since that parameter dictates the behavior of the /authorize endpoint, which doesn't get invoked during client_credentials flow. This currently is causing a test failure in touchstone.