Difference between revisions of "Notice-centric ID"
From MgmtWiki
(→Context) |
(→Problems) |
||
| Line 6: | Line 6: | ||
==Problems== | ==Problems== | ||
| − | * | + | * User Identity is immediately obvious from any social IDs. For example in Facebook there is a a requirement to like any Facebook ID to a real person. |
| − | |||
==Solutions== | ==Solutions== | ||
Revision as of 17:00, 16 February 2021
Full Title or Meme
The problem of giving notice to Subjects about issues is addressed before the user is asked to provide any personal information.
Context
It has become obvious that traditional methods of establishing identity have been focused on an Identifier Provider (IdP). This has created privacy and user tracking problems that have been difficult to mitigate. The most common method in 2020 is OpenID Connect using one of the social media sites like FaceBook or Google.
Problems
- User Identity is immediately obvious from any social IDs. For example in Facebook there is a a requirement to like any Facebook ID to a real person.
Solutions
- Before Subjects can be given notice, some mechanisms must be put into place to allow the subject to seek Redress or corrections to the data in the User Objects held by the Data Controller.
- One method for a web site to comply with Notice regulations is to create a Notice-centric ID. In this type of Identifier the issued to be addressed before the user is asked for personal data is for the notice channel to be established.
References
- See the wiki page on User Consent which is a structure that tells the user what data is held. This receipt is the first effort at providing Open Notice capabilities to users.
