Difference between revisions of "Bootstrapping Identity and Consent"
From MgmtWiki
(→Context) |
(→Solutions) |
||
| Line 12: | Line 12: | ||
==Solutions== | ==Solutions== | ||
| + | |||
| + | ===User Identifier Provider in Cloud=== | ||
| + | |||
| + | Where the user is on a device and the user's identifier provider is in the cloud, that provider will also have, at a minimum, user contact information to enable user [[Recovery]] and [[Redress]]. | ||
==References== | ==References== | ||
Revision as of 11:30, 7 July 2018
Contents
Full Title or Meme
A ceremony must be performed to establish identifiers and contact information among communicating parties before any other interactions can commence.
Context
- Given the greatly increased legislation that enforces the privacy rights of users of digital communications, some means is needed to identify and contact the parties to a covered interchange.
Problems
- Any identifying information about a user must not be released without that user's or a guardian's consent.
- At the end of the ceremony all parties have agreed and consented to their respective identifiers, contact methods and a trust relationship among them.
Solutions
User Identifier Provider in Cloud
Where the user is on a device and the user's identifier provider is in the cloud, that provider will also have, at a minimum, user contact information to enable user Recovery and Redress.
