Trust Frameworks Catalog: Difference between revisions
| Line 36: | Line 36: | ||
** eID schemes: https://ec.europa.eu/cefdigital/wiki/display/EIDCOMMUNITY/Overview+of+pre-notified+and+notified+eID+schemes+under+eIDAS | ** eID schemes: https://ec.europa.eu/cefdigital/wiki/display/EIDCOMMUNITY/Overview+of+pre-notified+and+notified+eID+schemes+under+eIDAS | ||
** list of trust service providers: https://webgate.ec.europa.eu/tl-browser/#/ | ** list of trust service providers: https://webgate.ec.europa.eu/tl-browser/#/ | ||
* Is the Native SSO, a continuation of NAPPS , in terms of goals and scope? | |||
9:49 AMTorsten Lodderstedt (yes.com) (to All): | |||
@Jules: The first link points to the list of notified eID implementations. If they would use OpenID Connect, the could use OpenID Connect 4 Identity Assurance. | |||
9:50 AMMike Jones (to All): | |||
Native SSO is related to NAPPS but with scaled-back goals, in that it's only trying to work for apps of the same organization. George Fletcher can provide more context. | |||
9:51 AMSathish (PG&E) (to All): | |||
Thanks | |||
9:51 AMGeorge Fletcher (to All): | |||
Native SSO isn't really an extension of NAPPS and it is currently limited to SSO between apps signed by the same vendor signing key. | |||
So as an explicit example, If you log into Yahoo Mail and then open Yahoo Finance, you can be seamlessly logged into Yahoo Finance without having to open a browser. | |||
==References== | ==References== | ||
Revision as of 17:25, 21 May 2020
Full Title
A list of both known trust frameworks and other catalogs of trust frameworks.
Trust Frameworks
"IDESG Status" is an indication of the use and value of the referenced TrustFramework to IDESG's own work.
| Title | Reference | Source | IDESG Status | Related Use Case(s) |
|---|---|---|---|---|
|
Kantara Initiative Identity Assurance Framework |
||||
|
InCommon |
Other Catelogs of Trust Frameworks
- ekyc-ida / identifiers from the OpenID Foundation.
- However there is a list of schemes and trust services that are covered by the eIDAS regulation.
- eID schemes: https://ec.europa.eu/cefdigital/wiki/display/EIDCOMMUNITY/Overview+of+pre-notified+and+notified+eID+schemes+under+eIDAS
- list of trust service providers: https://webgate.ec.europa.eu/tl-browser/#/
- Is the Native SSO, a continuation of NAPPS , in terms of goals and scope?
9:49 AMTorsten Lodderstedt (yes.com) (to All): @Jules: The first link points to the list of notified eID implementations. If they would use OpenID Connect, the could use OpenID Connect 4 Identity Assurance.
9:50 AMMike Jones (to All): Native SSO is related to NAPPS but with scaled-back goals, in that it's only trying to work for apps of the same organization. George Fletcher can provide more context.
9:51 AMSathish (PG&E) (to All): Thanks
9:51 AMGeorge Fletcher (to All): Native SSO isn't really an extension of NAPPS and it is currently limited to SSO between apps signed by the same vendor signing key. So as an explicit example, If you log into Yahoo Mail and then open Yahoo Finance, you can be seamlessly logged into Yahoo Finance without having to open a browser.