User Apps with Identifiers
Revision as of 23:26, 12 January 2021 by Tomjones (talk | contribs) (Created page with "==Full Title== This article addresses the various solutions to creation of a synchronized Identifier between a user app and a Relying Party ==Context== The example ad...")
Full Title
This article addresses the various solutions to creation of a synchronized Identifier between a user app and a Relying Party
Context
The example addressed here is a Smartphone app that is uses to establish a user's identifier with a Website over the internet.
Problems
- The user needs to trust that the app will honor the user's wishes.
- The web site needs to trust that the app correctly informs it of the user's preferred identifier with:
- the appropriate Identity Assurance Level (IAL) aka identity proofing.
- the appropriate Authentication Assurance Level (AAL) aka proof of presence and control by the user.
- the appropriate Federation Assurance Level (FAL) aka follows the federation rule and regulations.
Native App Solutions
The app is loaded from a trusted app store and has full access to the features of the device.
Web App Solutions
The app is loaded from a trusted web site and has access to the service broker features in the DOM.
Hybrid App Solutions
The app works with a