Short Description
The purpose of this test is to update an existing Policy to the Policy Repository with PPQ-3 and PPQ-4 transactions.
Goal
This test verifies the required steps for a Policy Source to update an existing Policy in the Policy Repository
Tested Components
- Policy Source
- Policy Repository
Prerequisite
he Mobile Privacy Policy Feed needs TLS for the communication. Make
sure that this option is set in your configuration for Proxy.
- You SHALL have a partner to perform this test.
- You can find samples of PPQm consents here.
- Bundles and consents have to be compliant with these implementation guides :
The PPQ-3/4 transactions SHALL provide IUA Token (ITI-72) for user authentication and authorization and SHALL record the events using ATX:FHIR Feed option (RESTful).
Description
The Policy Source sends an UpdatePolicy request to the Policy Repository. This request is used to update policies in the Policy Repository.
Evidence
The Policy Source shall present the following evidence:
- The Policy Source sends a Consent update request to the Policy Repository of the community.
- The Consent update request must update an existing policy in the Policy Repository of its community.
- The PPQ-3 response must be consistent with a success message.
- The Policy Source sends a Consent Bundle update request to the Policy Repository of the community.
- The Consent Bundle update request must update at least an existing policy in the Policy Repository of its community.
- The PPQ-4 Bundle response must be consistent with a success message.
- All the messages exchanged shall be validated in EVSClient.
Evaluation
In order to verify the test the Connectathon monitor will ask for the queries and responses of the UpdatePolicy requests