Difference between revisions of "Native App URI Handlers"
From MgmtWiki
(Created page with "==Full Title or Meme== A Native App can register to receive HTTP calls from the browser on the User Device, ==Context== * It is possible that web applications would...") |
(→References) |
||
| Line 23: | Line 23: | ||
[[Category:Glossary]] | [[Category:Glossary]] | ||
| + | [[Category:Authentication]] | ||
Revision as of 18:10, 17 December 2018
Full Title or Meme
A Native App can register to receive HTTP calls from the browser on the User Device,
Context
- It is possible that web applications would like to
Problems
Solutions
- Certification of the Native App please refer to page Native App Security.
- The Native App should perform all Authentication of the user by way of a browser (User Agent) selected by the user and running on the user's device using a trusted Identifier or Attribute Provider.
- Pre Oauth Entity Trust describes a means to represent third-party application endorsement for health care applications. POET’s goal is to help consumers distinguish between applications that have an endorsement versus applications that have no pedigree (i.e untrusted and could be malicious).
References
- Native App general page on this wiki
- Native App Security page on this wiki
- Native App Privacy page on this wiki
- W3C page on web apps best practices as of (2010-12-10).
- IETF RFC 8252 OAuth 2.0 for Native Apps https://tools.ietf.org/html/bcp212#section-7.2
- Apple App Store Review Guidelines https://developer.apple.com/app-store/review/guidelines/
