<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>idea Ability to inline AGOL Web Mapping Applications in html pages in ArcGIS Web AppBuilder Ideas</title>
    <link>https://community.esri.com/t5/arcgis-web-appbuilder-ideas/ability-to-inline-agol-web-mapping-applications-in/idi-p/922848</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Just as we can inline AGOL Web Maps in html pages, Id like to be able to do the same with AGOL&amp;nbsp;Web Mapping Applications (created in WebApp Builder). This would bring&amp;nbsp;GREAT&amp;nbsp;value to customers with Enterprise systems in which they wish to integrate AGOL's RICH mapcontent and functionality.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;To facilitate such integrations, enterprise users of system X would need to register their own AGOL credentials together with their credentials in X. X could then make a valid access token requets on behalf of users in X to AGOL, and thereby giving users in X seamless access (ie WITHOUT them getting prompted to login to AGOL) to their AGOL Web Mapping Applications inlined in system X UI.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;However, even though&amp;nbsp;making a correct token request from X to AGOL works fine, AGOL sends back a response header 'X-Frame-Options' set to 'DENY'. &amp;nbsp;This effectively prevents Web Mapping Application to be inlined in other html-pages, such as the X UI...&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Perhaps there is a way round this, but I still havent found what Im loking for...!&lt;/P&gt;&lt;P&gt;If someone solved it - great let me know!&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Rgds,&lt;/P&gt;&lt;P&gt;/Erik&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Mon, 24 Oct 2016 14:43:16 GMT</pubDate>
    <dc:creator>ErikLanhammar</dc:creator>
    <dc:date>2016-10-24T14:43:16Z</dc:date>
    <item>
      <title>Ability to inline AGOL Web Mapping Applications in html pages</title>
      <link>https://community.esri.com/t5/arcgis-web-appbuilder-ideas/ability-to-inline-agol-web-mapping-applications-in/idi-p/922848</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Just as we can inline AGOL Web Maps in html pages, Id like to be able to do the same with AGOL&amp;nbsp;Web Mapping Applications (created in WebApp Builder). This would bring&amp;nbsp;GREAT&amp;nbsp;value to customers with Enterprise systems in which they wish to integrate AGOL's RICH mapcontent and functionality.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;To facilitate such integrations, enterprise users of system X would need to register their own AGOL credentials together with their credentials in X. X could then make a valid access token requets on behalf of users in X to AGOL, and thereby giving users in X seamless access (ie WITHOUT them getting prompted to login to AGOL) to their AGOL Web Mapping Applications inlined in system X UI.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;However, even though&amp;nbsp;making a correct token request from X to AGOL works fine, AGOL sends back a response header 'X-Frame-Options' set to 'DENY'. &amp;nbsp;This effectively prevents Web Mapping Application to be inlined in other html-pages, such as the X UI...&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Perhaps there is a way round this, but I still havent found what Im loking for...!&lt;/P&gt;&lt;P&gt;If someone solved it - great let me know!&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Rgds,&lt;/P&gt;&lt;P&gt;/Erik&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 24 Oct 2016 14:43:16 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-web-appbuilder-ideas/ability-to-inline-agol-web-mapping-applications-in/idi-p/922848</guid>
      <dc:creator>ErikLanhammar</dc:creator>
      <dc:date>2016-10-24T14:43:16Z</dc:date>
    </item>
  </channel>
</rss>

