Skip to content

feat(qa-fhir): add SMART on FHIR scope prefixes to Fence config - #556

Draft
vincentvanhees wants to merge 1 commit into
masterfrom
feat/qa-fhir-inferno-smart-scopes
Draft

vincentvanhees wants to merge 1 commit into
masterfrom
feat/qa-fhir-inferno-smart-scopes

Conversation

@vincentvanhees

Copy link
Copy Markdown
Contributor

Add EXTRA_ALLOWED_SCOPE_PREFIXES and EXTRA_ALLOWED_SCOPES to the qa-fhir Fence config so that Inferno SMART clients can request patient-scoped tokens (e.g. patient/Patient.read). Required for the nightly Inferno US Core v6.1.0 CI workflow in gen3-code-vigil.

Link to Jira ticket if there is one:

Environments

qa-fhir

Description of changes

Adds EXTRA_ALLOWED_SCOPE_PREFIXES (patient/, user/, system/, launch/) and EXTRA_ALLOWED_SCOPES (SMART-specific scopes including fhirUser, launch, online_access, offline_access) to the qa-fhir Fence config.

Without these, Fence rejects SMART on FHIR scope requests from Inferno clients, blocking the nightly Inferno US Core v6.1.0 integration tests added in gen3-code-vigil. Fence must be redeployed to qa-fhir after merge for the change to take effect.

Add EXTRA_ALLOWED_SCOPE_PREFIXES and EXTRA_ALLOWED_SCOPES to the qa-fhir
Fence config so that Inferno SMART clients can request patient-scoped
tokens (e.g. patient/Patient.read). Required for the nightly Inferno
US Core v6.1.0 CI workflow in gen3-code-vigil.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant