Difference between revisions of "Financial User Consent"
(→Context) |
(→Context) |
||
| Line 6: | Line 6: | ||
** the IAP requests [[User Consent]] to [[Authorization|Authorize]] release of [[User Private Information]] and other [[Resource]]s to a [[Relying Party]] (RP). | ** the IAP requests [[User Consent]] to [[Authorization|Authorize]] release of [[User Private Information]] and other [[Resource]]s to a [[Relying Party]] (RP). | ||
** some fiduciary holder of user assets (Account Servicing Payment Service Provider (ASPSP)) needs [[User Consent]] to release those assets. | ** some fiduciary holder of user assets (Account Servicing Payment Service Provider (ASPSP)) needs [[User Consent]] to release those assets. | ||
| + | *** note that not all legal jurisdictions agree that a holder of user assets has a fiduciary responsibility to the user. | ||
*This page does not consider [[User Public Information]] or the [[Right to be Forgotten]]. | *This page does not consider [[User Public Information]] or the [[Right to be Forgotten]]. | ||
*During an authorization request by a [[Relying Party]], the [[Identifier or Attribute Provider]] requires user consent redirecting the user to the consent page. | *During an authorization request by a [[Relying Party]], the [[Identifier or Attribute Provider]] requires user consent redirecting the user to the consent page. | ||
Revision as of 11:09, 15 April 2019
Contents
Full Title or Meme
Financial User Consent extends the User Consent use case with significant exchange of value, typically payment data.
Context
- This page is about the use case of a User on a User Agent authenticated by an Identifier or Attribute Provider (IAP) with two areas of consent:
- the IAP requests User Consent to Authorize release of User Private Information and other Resources to a Relying Party (RP).
- some fiduciary holder of user assets (Account Servicing Payment Service Provider (ASPSP)) needs User Consent to release those assets.
- note that not all legal jurisdictions agree that a holder of user assets has a fiduciary responsibility to the user.
- This page does not consider User Public Information or the Right to be Forgotten.
- During an authorization request by a Relying Party, the Identifier or Attribute Provider requires user consent redirecting the user to the consent page.
- Consent is used to allow an end user to grant a client access to resources (identity or API).
Problem
User consent is discussed in the GDPR for transfers of User Information between two Data Controllers on the internet. It is not clear if the GDPR or other regulations apply to a site that collects user data for its own purposes and does not further process or share that User Information. Nor is any temporal relationship between User Consent acts described. So it is not clear if a new User Consent arrives, what action should be taken vis a vis any prior consents. If older consents are not invalidated, it is unclear how to evaluate conflict between the different consents.
Solution
In this wiki it is assumed that there can exist only one active User Consent among three parties on the internet, the Subject (aka User) the Identifier or Attribute Provider and the Relying Party. It is unclear if User Consent has any specific meaning between the Subject and the Identifier or Attribute Provider; that is left for further developments. In other words, if the user updates consent - all prior consents are unavailable for new actions.
Consent Page
In order for the user to grant consent, a consent page must be provided by the Identifier or Attribute Provider.
- A consent page normally renders the display name of the current user, the display name of the Relying Party (aka client) requesting access, the logo of the client, a link for more information about the client, and the list of resources the client is requesting access to. It’s also common to allow the user to indicate that their consent should be “remembered” so they are not prompted again in the future for the same client.
- Once the user has provided consent, the consent page must inform Identifier or Attribute Provider of the consent, and then the browser must be redirected back to allow the user to continue where they left off.
- The user's choice may be stored for later use by the same Web Site if the user opts into that option. If the user does not opt in, the choice as to scopes, date and destination MUST not be saved.
Back at the Relying Party
The User Consent provided might not align exactly with what the RP requested. In that case the RP may accept the consent granted, or it may need to go back to the user for additional Attributes or some Validation of the Attributes. It is important at this point to know if the session with the IAP is still valid, or if a new session would be initiated. The User Experience should be maximized whichever path is chosen.
Consent Taxonomy
- For the semi-static information the user must be shown a list of categories of User Private Information one the wiki page User Consent#Consent Taxonomy] start with a list of OpenID Connect Scopes and move on from there. This is typically user Attributes.
- For the transactional information the user must know what value is being transfered, both in terms of the money (or other value tokens) sent in one direction and the goods or services sent in exchange for that money. This transaction typically exposes user Behavior, which can still be very personal especially if the goods or services are related to health care issues.
References
Other Sources
- The wiki page on Open Banking discuses some of the transactional consent that the UK OBIE have documented.
- See the FHIR section on security and privacy for the HL7 take on privacy consent.
- Guidelines for obtaining meaningful consent from Office of the Privacy Commissioner of Canada which began to apply these guidelines on January 1, 2019.
- Meaningful Consent in the Digital Economy (MCDE) is an EPSRC-funded research project that is examining issues related to giving and obtaining user consent online.
