[CTF] Example and profiling of Provenance resource

[joofio]

Provenance to accomodate CTF

[joofio]

@amedranogil do you already have examples of this? If you do, please let us know. Otherwise, i can try to specify the profile and examples like Lenses and RMM

[amedranogil]

No examples yet, sorry

[joofio]

i will create profile (if needed) and example for you to comment

[joofio]

LINK: https://build.fhir.org/ig/hl7-eu/gravitate-health/branches/master/Provenance-signature.html
check if it makes sense

[gmej]

Regarding this task, I would like to confirm the following statement is true:
All backend services must authenticate with Keycloak. This is essential for provenance.

Is this true @margoraja? If this is true, we need to start planning for this as we should change the backend to authenticate services, which is not trivial.

[jkiddo]

FYI - the G Lens app facade that I use already logs in at keycloak when using the FOSPS

[margoraja]

Regarding this task, I would like to confirm the following statement is true: All backend services must authenticate with Keycloak. This is essential for provenance.

Is this true @margoraja? If this is true, we need to start planning for this as we should change the backend to authenticate services, which is not trivial.

Although I'm not sure from where that sentence is from but it sounds logical and seems to be valid claim. To sign something within CTF (or Content Trust or Data Integrity or Sign .. etc), it is essential that only users with permissions to do so have the access for that. However no such authentication shall be necessary or required for verifications. Verification shall be open for anyone (limited to for users within deployed instance, by firewall rules or configured to be truely open).
Content trust, that we delivered, is already enforcing this. Our service checks wether or not incoming singing request has a token that is allowed to perform signing. It does not require any authentication for verification.
https://github.com/Gravitate-Health/content-trust
Edit: Component does not require any specific who resource in FHIR provenance resource to be defined, it does not define it nor does any validation or evaluations (data in signature (in porvenance) is not compared against who resource under provenance).
Edit2: Content Trust component already signs and verifies the whole FHIR resource, its provenance reousrce or both. That is implemented.