Difference between revisions of "Cross-Origin iFrame"

Revision as of 09:35, 12 March 2021

The Inline Frame, or iFrame was introduced to allow isolated web pages from unrelated entities to embed content seamlessly into a web page.

Frames and Framesets were introduced early in browser history to enable refreshing only a portion of a web page to improve responsiveness of web pages in the days of low bandwidth data communications.
Identity features like OpenID Connect and WebAuthn 2 depends on the Cross-Origin iFrame for a seamless User Experience when identity is provided by a different web site than the Relying Party.
Early one security was addressed If they’re not from the same domain, the parent HTML document and the iframe don’t have access to each other’s CSS styles, DOM or JavaScript functions, cookies, or local storage.

Iframes as a Security Feature does actually acknowledge some of the security problems with iFrames.

@@ Line 4: / Line 4: @@
 ==Context==
 * Frames and Framesets were introduced early in browser history to enable refreshing only a portion of a web page to improve responsiveness of web pages in the days of low bandwidth data communications.
-* [[Identity]] features like [[OpenID Connect]] and [[WebAuthn 2]] depends on the [[Cross-Origin iFrame]] for a seamless [[User Experience]] when identity is provided by a different web site than the [[Realying Party]].
+* [[Identity]] features like [[OpenID Connect]] and [[WebAuthn 2]] depends on the [[Cross-Origin iFrame]] for a seamless [[User Experience]] when identity is provided by a different web site than the [[Relying Party]].
+* Early one security was addressed If they’re not from the same domain, the parent HTML document and the iframe don’t have access to each other’s CSS styles, DOM or JavaScript functions, cookies, or local storage.
 ==References==