ConsumerDataStandardsAustralia / infosec

Work space for the consumer data right information security profile development in Australia
MIT License
16 stars 5 forks source link

Granularity of consent revocation and reauthorization #69

Open sachi-d opened 4 years ago

sachi-d commented 4 years ago

Hypothesis

In [1] it is stated that

There will be no consent APIs to modify consent post authorisation. Consent will be considered immutable until a revocation or reauthorisation event occurs

What changes to consent are allowed in revocation and reauthorization?

E.g. If the consumer selects multiple accounts during authorization, can he revoke singular accounts during consent revocation or should he revoke the entire consent altogether?

[1] - https://github.com/ConsumerDataStandardsAustralia/infosec/issues/47#issuecomment-479275972

Description

A clear and concise description of the hypothesis. Example: Based on initial feedback Java is the most prevalent language in use within implementing organisations. In addition Java is a language where engineering resources are readily available. On this basis the project will develop it's core assets in Java and focus on delivering assets for use by industry in Java first.

Available Options

Present a list of considered options with an optional indication of what is currently preferred Example: Initial assets from the CDS Engineering team will be produced using the Java language.

sachi-d commented 4 years ago

Kind reminder on the above.