668
edits
Identity/AttachedServices/Architecture: Difference between revisions
Identity/AttachedServices/Architecture (view source)
Revision as of 00:32, 26 March 2013
, 26 March 2013→Authentication
| Line 10: | Line 10: | ||
These requirements (and the next Data Security section) call for a design where the browser locally captures the user's email and password, then engages in a protocol with the IdP – persona.org or otherwise – to obtain a certificate. One way to implement this immediately is to embed the invisible persona.org communication IFRAME and call into its internal API, which we recently augmented to include login() and accountExists() calls to support this implementation path. | These requirements (and the next Data Security section) call for a design where the browser locally captures the user's email and password, then engages in a protocol with the IdP – persona.org or otherwise – to obtain a certificate. One way to implement this immediately is to embed the invisible persona.org communication IFRAME and call into its internal API, which we recently augmented to include login() and accountExists() calls to support this implementation path. | ||
[[Image:Iframe-login-embedding.png]] | |||
== Data Security == | == Data Security == | ||