use scopes and introduce a pairwise pseudonymous identifer #92
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What type of PR is this?
Add one of the following kinds:
What this PR does / why we need it:
For privacy reasons the API consumer should be able to specify which data fields should be returned. Only required data should be asked for and returned by the API.
See Art. 5 GDPR Principles relating to processing of personal data.
See UK Information Commisioner's Office
As always in CAMARA the allowed scopes for an API consumer are determined a Onboarding Time.
For privacy reasons globally unique and permanent identifiers should be avoided.
IMEI and IMEISV are such globally unique and permanent identifiers.
Globally unique and permanent identifiers allow user tracking across API consumers.
Colluding API consumers can track the user.
This PR uses scopes which allow the API consumer to specify which data they want in the API result.
This PR introduces the identifier PPID (pairwise pseudonymous identifier) which is local to the API producer or if based on a sector_identifier to a group of API consumers.
Additional Context
#36