<?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 Streamlining authentication between ArcGIS Online and Portal to support embedded content in ArcGIS Experience Builder Ideas</title>
    <link>https://community.esri.com/t5/arcgis-experience-builder-ideas/streamlining-authentication-between-arcgis-online/idi-p/1685007</link>
    <description>&lt;P&gt;&lt;SPAN&gt;Our team recently&amp;nbsp;encountered&amp;nbsp;a&amp;nbsp;significant limitation in&amp;nbsp;&lt;/SPAN&gt;&lt;STRONG&gt;&lt;SPAN&gt;ArcGIS Experience Builder&lt;/SPAN&gt;&lt;/STRONG&gt;&lt;SPAN&gt;&amp;nbsp;and&amp;nbsp;&lt;/SPAN&gt;&lt;STRONG&gt;&lt;SPAN&gt;Operations Dashboards&lt;/SPAN&gt;&lt;/STRONG&gt;&lt;SPAN&gt;&amp;nbsp;that affects organizations using&amp;nbsp;&lt;/SPAN&gt;&lt;STRONG&gt;&lt;SPAN&gt;hybrid AGOL + Portal architectures&lt;/SPAN&gt;&lt;/STRONG&gt;&lt;SPAN&gt;. After working extensively with Esri Support (Case #04081687),&amp;nbsp;we’ve&amp;nbsp;confirmed that the current embed widget does&amp;nbsp;&lt;/SPAN&gt;&lt;STRONG&gt;&lt;SPAN&gt;not support passing credentials from ArcGIS Online (AGOL) into Portal&lt;/SPAN&gt;&lt;/STRONG&gt;&lt;SPAN&gt;&amp;nbsp;to retrieve embedded content. This gap&amp;nbsp;creates&amp;nbsp;&amp;nbsp;challenges&amp;nbsp;for&amp;nbsp;organizations&amp;nbsp;that need to securely display internal content in AGOL-hosted apps.&lt;/SPAN&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;&lt;SPAN&gt;The Problem&lt;/SPAN&gt;&lt;/STRONG&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;We collect hundreds of thousands of photos every year&amp;nbsp;using&amp;nbsp;&lt;/SPAN&gt;&lt;STRONG&gt;&lt;SPAN&gt;Survey123&lt;/SPAN&gt;&lt;/STRONG&gt;&lt;SPAN&gt;.&amp;nbsp;To manage this quantity of photos, we ingest,&amp;nbsp;rename&amp;nbsp;and store them in our&amp;nbsp;&lt;/SPAN&gt;&lt;STRONG&gt;&lt;SPAN&gt;Azure file system&lt;/SPAN&gt;&lt;/STRONG&gt;&lt;SPAN&gt;&amp;nbsp;in folders by site.&amp;nbsp;Rather than have users manually open each photo, we generate HTML pages of each folders&amp;nbsp;contents. These HTML pages display thumbnails of all photos within its respective directory, photo names, photo&amp;nbsp;comments&amp;nbsp;and links to open the source photo. This photo directory&amp;nbsp;including the HTML pages are web&amp;nbsp;enabled&amp;nbsp;using&amp;nbsp;&lt;/SPAN&gt;&lt;STRONG&gt;&lt;SPAN&gt;Esri Attachment Manager SOE&lt;/SPAN&gt;&lt;/STRONG&gt;&lt;SPAN&gt;&amp;nbsp;for&amp;nbsp;and the HTML pages can be embedded into a&amp;nbsp;various applications&amp;nbsp;to improve photo access.&amp;nbsp;When embedding HTML&amp;nbsp;pages&amp;nbsp;&amp;nbsp;hosted&amp;nbsp;on an internal&amp;nbsp;&lt;/SPAN&gt;&lt;STRONG&gt;&lt;SPAN&gt;Portal for ArcGIS&lt;/SPAN&gt;&lt;/STRONG&gt;&lt;SPAN&gt;, AGOL apps&amp;nbsp;fail to&amp;nbsp;display the content because credentials are not passed through. While other data layers from Portal authenticate correctly, the embedded HTML pages trigger repeated authentication loops and&amp;nbsp;ultimately fail&amp;nbsp;to load.&lt;/SPAN&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;&lt;SPAN&gt;What We Tried&lt;/SPAN&gt;&lt;/STRONG&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;&lt;SPAN&gt;Adjusting&amp;nbsp;&lt;/SPAN&gt;&lt;STRONG&gt;&lt;SPAN&gt;X-FRAME-OPTIONS&lt;/SPAN&gt;&lt;/STRONG&gt;&lt;SPAN&gt;&amp;nbsp;headers via IIS on the Portal Web Adaptor allowed partial progress but introduced global risks and conflicts.&lt;/SPAN&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;UL&gt;&lt;LI&gt;&lt;SPAN&gt;Alternative approaches using&amp;nbsp;&lt;/SPAN&gt;&lt;STRONG&gt;&lt;SPAN&gt;Content-Security-Policy frame-ancestors&lt;/SPAN&gt;&lt;/STRONG&gt;&lt;SPAN&gt;&amp;nbsp;also fell short.&lt;/SPAN&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;UL&gt;&lt;LI&gt;&lt;SPAN&gt;The root issue: No configurable&amp;nbsp;option&amp;nbsp;exists in Experience Builder or Dashboards to enable credential passthrough between AGOL and Portal.&lt;/SPAN&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;&lt;STRONG&gt;&lt;SPAN&gt;Proposed Solution&lt;/SPAN&gt;&lt;/STRONG&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Esri should provide:&lt;/SPAN&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;&lt;SPAN&gt;A&amp;nbsp;&lt;/SPAN&gt;&lt;STRONG&gt;&lt;SPAN&gt;configurable setting&lt;/SPAN&gt;&lt;/STRONG&gt;&lt;SPAN&gt;&amp;nbsp;in the&amp;nbsp;&lt;/SPAN&gt;&lt;STRONG&gt;&lt;SPAN&gt;embed widget&lt;/SPAN&gt;&lt;/STRONG&gt;&lt;SPAN&gt;&amp;nbsp;to allow trusted credential passthrough.&lt;/SPAN&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;UL&gt;&lt;LI&gt;&lt;SPAN&gt;A&amp;nbsp;&lt;/SPAN&gt;&lt;STRONG&gt;&lt;SPAN&gt;global&amp;nbsp;option&lt;/SPAN&gt;&lt;/STRONG&gt;&lt;SPAN&gt;&amp;nbsp;in Experience Builder/Operations Dashboards&amp;nbsp;to manage headers like X-FRAME-OPTIONS or similar security directives.&lt;/SPAN&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;&lt;STRONG&gt;&lt;SPAN&gt;Why This Matters&lt;/SPAN&gt;&lt;/STRONG&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;This limitation forces organizations to:&lt;/SPAN&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;&lt;SPAN&gt;Duplicate applications&amp;nbsp;across environments.&lt;/SPAN&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;UL&gt;&lt;LI&gt;&lt;SPAN&gt;Use insecure workarounds that compromise governance.&lt;/SPAN&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;UL&gt;&lt;LI&gt;&lt;SPAN&gt;Spend&amp;nbsp;additional&amp;nbsp;resources&amp;nbsp;maintaining&amp;nbsp;parallel systems.&lt;/SPAN&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;&lt;STRONG&gt;&lt;SPAN&gt;Use Case&lt;/SPAN&gt;&lt;/STRONG&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Our organization recently migrated from&amp;nbsp;&lt;/SPAN&gt;&lt;STRONG&gt;&lt;SPAN&gt;in-house servers with IIS capabilities&lt;/SPAN&gt;&lt;/STRONG&gt;&lt;SPAN&gt;&amp;nbsp;to an&amp;nbsp;&lt;/SPAN&gt;&lt;STRONG&gt;&lt;SPAN&gt;ArcGIS Enterprise Portal architecture hosted in&amp;nbsp;a&amp;nbsp;Microsoft&amp;nbsp;Azure&amp;nbsp;environment&lt;/SPAN&gt;&lt;/STRONG&gt;&lt;SPAN&gt;, and&amp;nbsp;we’ve&amp;nbsp;begun&amp;nbsp;leveraging&amp;nbsp;the&amp;nbsp;&lt;/SPAN&gt;&lt;STRONG&gt;&lt;SPAN&gt;Esri Attachment Manager SOE&lt;/SPAN&gt;&lt;/STRONG&gt;&lt;SPAN&gt;&amp;nbsp;for managing embedded HTML content. Historically, this workflow was seamless:&lt;/SPAN&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;&lt;SPAN&gt;We&amp;nbsp;maintained&amp;nbsp;&lt;/SPAN&gt;&lt;STRONG&gt;&lt;SPAN&gt;a suite of applications&lt;/SPAN&gt;&lt;/STRONG&gt;&lt;SPAN&gt;&amp;nbsp;built&amp;nbsp;in&amp;nbsp;our&amp;nbsp;Organizational&amp;nbsp;&lt;/SPAN&gt;&lt;STRONG&gt;&lt;SPAN&gt;ArcGIS Online (AGOL)&lt;/SPAN&gt;&lt;/STRONG&gt;&lt;SPAN&gt;&amp;nbsp;site&amp;nbsp;accessible to&amp;nbsp;internal staff and&amp;nbsp;shared to&amp;nbsp;external&amp;nbsp;partners&amp;nbsp;via&amp;nbsp;&lt;/SPAN&gt;&lt;STRONG&gt;&lt;SPAN&gt;GeoPlatform&amp;nbsp;ArcGIS Online&amp;nbsp;Organization&lt;/SPAN&gt;&lt;/STRONG&gt;&lt;SPAN&gt;.&lt;/SPAN&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;UL&gt;&lt;LI&gt;&lt;SPAN&gt;Internal users could view embedded HTML content within&amp;nbsp;&lt;/SPAN&gt;&lt;STRONG&gt;&lt;SPAN&gt;Operations Dashboards&lt;/SPAN&gt;&lt;/STRONG&gt;&lt;SPAN&gt;&amp;nbsp;and&amp;nbsp;&lt;/SPAN&gt;&lt;STRONG&gt;&lt;SPAN&gt;Experience Builder (ExB)&lt;/SPAN&gt;&lt;/STRONG&gt;&lt;SPAN&gt;&amp;nbsp;because their authentication tokens passed through successfully.&lt;/SPAN&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;UL&gt;&lt;LI&gt;&lt;SPAN&gt;External contractors, who lacked credentials, would simply see a warning message&amp;nbsp;which is&amp;nbsp;an acceptable outcome for our use case.&lt;/SPAN&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;&lt;SPAN&gt;This approach allowed us to&amp;nbsp;maintain&amp;nbsp;&lt;/SPAN&gt;&lt;STRONG&gt;&lt;SPAN&gt;a&amp;nbsp;central&amp;nbsp;repository of&amp;nbsp;applications&lt;/SPAN&gt;&lt;/STRONG&gt;&lt;SPAN&gt;&amp;nbsp;for all users rather than building multiple, user-specific apps across different environments.&lt;/SPAN&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Since moving to the&amp;nbsp;Microsoft&amp;nbsp;&lt;/SPAN&gt;&lt;STRONG&gt;&lt;SPAN&gt;Azure-hosted Portal environment&lt;/SPAN&gt;&lt;/STRONG&gt;&lt;SPAN&gt;,&amp;nbsp;we’ve&amp;nbsp;encountered&amp;nbsp;a&amp;nbsp;limitation:&lt;/SPAN&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;&lt;SPAN&gt;Dashboards and&amp;nbsp;ExB&amp;nbsp;apps built in AGOL can still authenticate users to pull data from internal&amp;nbsp;&lt;/SPAN&gt;&lt;STRONG&gt;&lt;SPAN&gt;REST services&lt;/SPAN&gt;&lt;/STRONG&gt;&lt;SPAN&gt;.&lt;/SPAN&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;UL&gt;&lt;LI&gt;&lt;SPAN&gt;However, they&amp;nbsp;&lt;/SPAN&gt;&lt;STRONG&gt;&lt;SPAN&gt;cannot pass that same authentication&lt;/SPAN&gt;&lt;/STRONG&gt;&lt;SPAN&gt;&amp;nbsp;to retrieve content from the&amp;nbsp;&lt;/SPAN&gt;&lt;STRONG&gt;&lt;SPAN&gt;Attachment Manager SOE&lt;/SPAN&gt;&lt;/STRONG&gt;&lt;SPAN&gt;.&lt;/SPAN&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;UL&gt;&lt;LI&gt;&lt;SPAN&gt;As a result, embedded HTML pages/widgets&amp;nbsp;fail to&amp;nbsp;load for internal users, breaking workflows that previously worked flawlessly.&lt;/SPAN&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;&lt;SPAN&gt;To replicate our&amp;nbsp;previous&amp;nbsp;functionality, we now&amp;nbsp;have to:&lt;/SPAN&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;&lt;SPAN&gt;Build&amp;nbsp;&lt;/SPAN&gt;&lt;STRONG&gt;&lt;SPAN&gt;separate apps&lt;/SPAN&gt;&lt;/STRONG&gt;&lt;SPAN&gt;&amp;nbsp;within the Portal environment for internal users.&lt;/SPAN&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;UL&gt;&lt;LI&gt;&lt;SPAN&gt;Maintain&amp;nbsp;&lt;/SPAN&gt;&lt;STRONG&gt;&lt;SPAN&gt;duplicate workflows&lt;/SPAN&gt;&lt;/STRONG&gt;&lt;SPAN&gt;&amp;nbsp;or split&amp;nbsp;processes across multiple interfaces.&lt;/SPAN&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;&lt;SPAN&gt;This adds unnecessary complexity, increases maintenance overhead, and undermines the efficiency of our centralized&amp;nbsp;application&amp;nbsp;strategy.&lt;/SPAN&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Our field&amp;nbsp;staff and partners&amp;nbsp;rely&amp;nbsp;on these tools for mission-critical operations. The inability to pass credentials for embedded content forces&amp;nbsp;a fragmented architecture. A solution that enables&amp;nbsp;&lt;/SPAN&gt;&lt;STRONG&gt;&lt;SPAN&gt;credential passthrough for embedded content&lt;/SPAN&gt;&lt;/STRONG&gt;&lt;SPAN&gt;&amp;nbsp;would restore the simplicity and reliability we had before migration.&lt;/SPAN&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;</description>
    <pubDate>Wed, 18 Feb 2026 19:55:24 GMT</pubDate>
    <dc:creator>LoganShank</dc:creator>
    <dc:date>2026-02-18T19:55:24Z</dc:date>
    <item>
      <title>Streamlining authentication between ArcGIS Online and Portal to support embedded content</title>
      <link>https://community.esri.com/t5/arcgis-experience-builder-ideas/streamlining-authentication-between-arcgis-online/idi-p/1685007</link>
      <description>&lt;P&gt;&lt;SPAN&gt;Our team recently&amp;nbsp;encountered&amp;nbsp;a&amp;nbsp;significant limitation in&amp;nbsp;&lt;/SPAN&gt;&lt;STRONG&gt;&lt;SPAN&gt;ArcGIS Experience Builder&lt;/SPAN&gt;&lt;/STRONG&gt;&lt;SPAN&gt;&amp;nbsp;and&amp;nbsp;&lt;/SPAN&gt;&lt;STRONG&gt;&lt;SPAN&gt;Operations Dashboards&lt;/SPAN&gt;&lt;/STRONG&gt;&lt;SPAN&gt;&amp;nbsp;that affects organizations using&amp;nbsp;&lt;/SPAN&gt;&lt;STRONG&gt;&lt;SPAN&gt;hybrid AGOL + Portal architectures&lt;/SPAN&gt;&lt;/STRONG&gt;&lt;SPAN&gt;. After working extensively with Esri Support (Case #04081687),&amp;nbsp;we’ve&amp;nbsp;confirmed that the current embed widget does&amp;nbsp;&lt;/SPAN&gt;&lt;STRONG&gt;&lt;SPAN&gt;not support passing credentials from ArcGIS Online (AGOL) into Portal&lt;/SPAN&gt;&lt;/STRONG&gt;&lt;SPAN&gt;&amp;nbsp;to retrieve embedded content. This gap&amp;nbsp;creates&amp;nbsp;&amp;nbsp;challenges&amp;nbsp;for&amp;nbsp;organizations&amp;nbsp;that need to securely display internal content in AGOL-hosted apps.&lt;/SPAN&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;&lt;SPAN&gt;The Problem&lt;/SPAN&gt;&lt;/STRONG&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;We collect hundreds of thousands of photos every year&amp;nbsp;using&amp;nbsp;&lt;/SPAN&gt;&lt;STRONG&gt;&lt;SPAN&gt;Survey123&lt;/SPAN&gt;&lt;/STRONG&gt;&lt;SPAN&gt;.&amp;nbsp;To manage this quantity of photos, we ingest,&amp;nbsp;rename&amp;nbsp;and store them in our&amp;nbsp;&lt;/SPAN&gt;&lt;STRONG&gt;&lt;SPAN&gt;Azure file system&lt;/SPAN&gt;&lt;/STRONG&gt;&lt;SPAN&gt;&amp;nbsp;in folders by site.&amp;nbsp;Rather than have users manually open each photo, we generate HTML pages of each folders&amp;nbsp;contents. These HTML pages display thumbnails of all photos within its respective directory, photo names, photo&amp;nbsp;comments&amp;nbsp;and links to open the source photo. This photo directory&amp;nbsp;including the HTML pages are web&amp;nbsp;enabled&amp;nbsp;using&amp;nbsp;&lt;/SPAN&gt;&lt;STRONG&gt;&lt;SPAN&gt;Esri Attachment Manager SOE&lt;/SPAN&gt;&lt;/STRONG&gt;&lt;SPAN&gt;&amp;nbsp;for&amp;nbsp;and the HTML pages can be embedded into a&amp;nbsp;various applications&amp;nbsp;to improve photo access.&amp;nbsp;When embedding HTML&amp;nbsp;pages&amp;nbsp;&amp;nbsp;hosted&amp;nbsp;on an internal&amp;nbsp;&lt;/SPAN&gt;&lt;STRONG&gt;&lt;SPAN&gt;Portal for ArcGIS&lt;/SPAN&gt;&lt;/STRONG&gt;&lt;SPAN&gt;, AGOL apps&amp;nbsp;fail to&amp;nbsp;display the content because credentials are not passed through. While other data layers from Portal authenticate correctly, the embedded HTML pages trigger repeated authentication loops and&amp;nbsp;ultimately fail&amp;nbsp;to load.&lt;/SPAN&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;&lt;SPAN&gt;What We Tried&lt;/SPAN&gt;&lt;/STRONG&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;&lt;SPAN&gt;Adjusting&amp;nbsp;&lt;/SPAN&gt;&lt;STRONG&gt;&lt;SPAN&gt;X-FRAME-OPTIONS&lt;/SPAN&gt;&lt;/STRONG&gt;&lt;SPAN&gt;&amp;nbsp;headers via IIS on the Portal Web Adaptor allowed partial progress but introduced global risks and conflicts.&lt;/SPAN&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;UL&gt;&lt;LI&gt;&lt;SPAN&gt;Alternative approaches using&amp;nbsp;&lt;/SPAN&gt;&lt;STRONG&gt;&lt;SPAN&gt;Content-Security-Policy frame-ancestors&lt;/SPAN&gt;&lt;/STRONG&gt;&lt;SPAN&gt;&amp;nbsp;also fell short.&lt;/SPAN&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;UL&gt;&lt;LI&gt;&lt;SPAN&gt;The root issue: No configurable&amp;nbsp;option&amp;nbsp;exists in Experience Builder or Dashboards to enable credential passthrough between AGOL and Portal.&lt;/SPAN&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;&lt;STRONG&gt;&lt;SPAN&gt;Proposed Solution&lt;/SPAN&gt;&lt;/STRONG&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Esri should provide:&lt;/SPAN&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;&lt;SPAN&gt;A&amp;nbsp;&lt;/SPAN&gt;&lt;STRONG&gt;&lt;SPAN&gt;configurable setting&lt;/SPAN&gt;&lt;/STRONG&gt;&lt;SPAN&gt;&amp;nbsp;in the&amp;nbsp;&lt;/SPAN&gt;&lt;STRONG&gt;&lt;SPAN&gt;embed widget&lt;/SPAN&gt;&lt;/STRONG&gt;&lt;SPAN&gt;&amp;nbsp;to allow trusted credential passthrough.&lt;/SPAN&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;UL&gt;&lt;LI&gt;&lt;SPAN&gt;A&amp;nbsp;&lt;/SPAN&gt;&lt;STRONG&gt;&lt;SPAN&gt;global&amp;nbsp;option&lt;/SPAN&gt;&lt;/STRONG&gt;&lt;SPAN&gt;&amp;nbsp;in Experience Builder/Operations Dashboards&amp;nbsp;to manage headers like X-FRAME-OPTIONS or similar security directives.&lt;/SPAN&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;&lt;STRONG&gt;&lt;SPAN&gt;Why This Matters&lt;/SPAN&gt;&lt;/STRONG&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;This limitation forces organizations to:&lt;/SPAN&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;&lt;SPAN&gt;Duplicate applications&amp;nbsp;across environments.&lt;/SPAN&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;UL&gt;&lt;LI&gt;&lt;SPAN&gt;Use insecure workarounds that compromise governance.&lt;/SPAN&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;UL&gt;&lt;LI&gt;&lt;SPAN&gt;Spend&amp;nbsp;additional&amp;nbsp;resources&amp;nbsp;maintaining&amp;nbsp;parallel systems.&lt;/SPAN&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;&lt;STRONG&gt;&lt;SPAN&gt;Use Case&lt;/SPAN&gt;&lt;/STRONG&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Our organization recently migrated from&amp;nbsp;&lt;/SPAN&gt;&lt;STRONG&gt;&lt;SPAN&gt;in-house servers with IIS capabilities&lt;/SPAN&gt;&lt;/STRONG&gt;&lt;SPAN&gt;&amp;nbsp;to an&amp;nbsp;&lt;/SPAN&gt;&lt;STRONG&gt;&lt;SPAN&gt;ArcGIS Enterprise Portal architecture hosted in&amp;nbsp;a&amp;nbsp;Microsoft&amp;nbsp;Azure&amp;nbsp;environment&lt;/SPAN&gt;&lt;/STRONG&gt;&lt;SPAN&gt;, and&amp;nbsp;we’ve&amp;nbsp;begun&amp;nbsp;leveraging&amp;nbsp;the&amp;nbsp;&lt;/SPAN&gt;&lt;STRONG&gt;&lt;SPAN&gt;Esri Attachment Manager SOE&lt;/SPAN&gt;&lt;/STRONG&gt;&lt;SPAN&gt;&amp;nbsp;for managing embedded HTML content. Historically, this workflow was seamless:&lt;/SPAN&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;&lt;SPAN&gt;We&amp;nbsp;maintained&amp;nbsp;&lt;/SPAN&gt;&lt;STRONG&gt;&lt;SPAN&gt;a suite of applications&lt;/SPAN&gt;&lt;/STRONG&gt;&lt;SPAN&gt;&amp;nbsp;built&amp;nbsp;in&amp;nbsp;our&amp;nbsp;Organizational&amp;nbsp;&lt;/SPAN&gt;&lt;STRONG&gt;&lt;SPAN&gt;ArcGIS Online (AGOL)&lt;/SPAN&gt;&lt;/STRONG&gt;&lt;SPAN&gt;&amp;nbsp;site&amp;nbsp;accessible to&amp;nbsp;internal staff and&amp;nbsp;shared to&amp;nbsp;external&amp;nbsp;partners&amp;nbsp;via&amp;nbsp;&lt;/SPAN&gt;&lt;STRONG&gt;&lt;SPAN&gt;GeoPlatform&amp;nbsp;ArcGIS Online&amp;nbsp;Organization&lt;/SPAN&gt;&lt;/STRONG&gt;&lt;SPAN&gt;.&lt;/SPAN&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;UL&gt;&lt;LI&gt;&lt;SPAN&gt;Internal users could view embedded HTML content within&amp;nbsp;&lt;/SPAN&gt;&lt;STRONG&gt;&lt;SPAN&gt;Operations Dashboards&lt;/SPAN&gt;&lt;/STRONG&gt;&lt;SPAN&gt;&amp;nbsp;and&amp;nbsp;&lt;/SPAN&gt;&lt;STRONG&gt;&lt;SPAN&gt;Experience Builder (ExB)&lt;/SPAN&gt;&lt;/STRONG&gt;&lt;SPAN&gt;&amp;nbsp;because their authentication tokens passed through successfully.&lt;/SPAN&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;UL&gt;&lt;LI&gt;&lt;SPAN&gt;External contractors, who lacked credentials, would simply see a warning message&amp;nbsp;which is&amp;nbsp;an acceptable outcome for our use case.&lt;/SPAN&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;&lt;SPAN&gt;This approach allowed us to&amp;nbsp;maintain&amp;nbsp;&lt;/SPAN&gt;&lt;STRONG&gt;&lt;SPAN&gt;a&amp;nbsp;central&amp;nbsp;repository of&amp;nbsp;applications&lt;/SPAN&gt;&lt;/STRONG&gt;&lt;SPAN&gt;&amp;nbsp;for all users rather than building multiple, user-specific apps across different environments.&lt;/SPAN&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Since moving to the&amp;nbsp;Microsoft&amp;nbsp;&lt;/SPAN&gt;&lt;STRONG&gt;&lt;SPAN&gt;Azure-hosted Portal environment&lt;/SPAN&gt;&lt;/STRONG&gt;&lt;SPAN&gt;,&amp;nbsp;we’ve&amp;nbsp;encountered&amp;nbsp;a&amp;nbsp;limitation:&lt;/SPAN&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;&lt;SPAN&gt;Dashboards and&amp;nbsp;ExB&amp;nbsp;apps built in AGOL can still authenticate users to pull data from internal&amp;nbsp;&lt;/SPAN&gt;&lt;STRONG&gt;&lt;SPAN&gt;REST services&lt;/SPAN&gt;&lt;/STRONG&gt;&lt;SPAN&gt;.&lt;/SPAN&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;UL&gt;&lt;LI&gt;&lt;SPAN&gt;However, they&amp;nbsp;&lt;/SPAN&gt;&lt;STRONG&gt;&lt;SPAN&gt;cannot pass that same authentication&lt;/SPAN&gt;&lt;/STRONG&gt;&lt;SPAN&gt;&amp;nbsp;to retrieve content from the&amp;nbsp;&lt;/SPAN&gt;&lt;STRONG&gt;&lt;SPAN&gt;Attachment Manager SOE&lt;/SPAN&gt;&lt;/STRONG&gt;&lt;SPAN&gt;.&lt;/SPAN&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;UL&gt;&lt;LI&gt;&lt;SPAN&gt;As a result, embedded HTML pages/widgets&amp;nbsp;fail to&amp;nbsp;load for internal users, breaking workflows that previously worked flawlessly.&lt;/SPAN&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;&lt;SPAN&gt;To replicate our&amp;nbsp;previous&amp;nbsp;functionality, we now&amp;nbsp;have to:&lt;/SPAN&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;&lt;SPAN&gt;Build&amp;nbsp;&lt;/SPAN&gt;&lt;STRONG&gt;&lt;SPAN&gt;separate apps&lt;/SPAN&gt;&lt;/STRONG&gt;&lt;SPAN&gt;&amp;nbsp;within the Portal environment for internal users.&lt;/SPAN&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;UL&gt;&lt;LI&gt;&lt;SPAN&gt;Maintain&amp;nbsp;&lt;/SPAN&gt;&lt;STRONG&gt;&lt;SPAN&gt;duplicate workflows&lt;/SPAN&gt;&lt;/STRONG&gt;&lt;SPAN&gt;&amp;nbsp;or split&amp;nbsp;processes across multiple interfaces.&lt;/SPAN&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;&lt;SPAN&gt;This adds unnecessary complexity, increases maintenance overhead, and undermines the efficiency of our centralized&amp;nbsp;application&amp;nbsp;strategy.&lt;/SPAN&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Our field&amp;nbsp;staff and partners&amp;nbsp;rely&amp;nbsp;on these tools for mission-critical operations. The inability to pass credentials for embedded content forces&amp;nbsp;a fragmented architecture. A solution that enables&amp;nbsp;&lt;/SPAN&gt;&lt;STRONG&gt;&lt;SPAN&gt;credential passthrough for embedded content&lt;/SPAN&gt;&lt;/STRONG&gt;&lt;SPAN&gt;&amp;nbsp;would restore the simplicity and reliability we had before migration.&lt;/SPAN&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 18 Feb 2026 19:55:24 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-experience-builder-ideas/streamlining-authentication-between-arcgis-online/idi-p/1685007</guid>
      <dc:creator>LoganShank</dc:creator>
      <dc:date>2026-02-18T19:55:24Z</dc:date>
    </item>
    <item>
      <title>Re: Streamlining authentication between ArcGIS Online and Portal to support embedded content</title>
      <link>https://community.esri.com/t5/arcgis-experience-builder-ideas/streamlining-authentication-between-arcgis-online/idc-p/1685165#M5037</link>
      <description>&lt;P&gt;Big upvote for this one.&amp;nbsp; We are consistently seeing issues in ExB when we mix content from AGOL and/or multiple portals.&amp;nbsp; We work nationwide so we have up to 12 state portals that we use data from or them from us.&amp;nbsp; We also coordinate with multiple agencies - again all with there own portals.&amp;nbsp; Did not have issues in WAB so it must be possible.&lt;/P&gt;&lt;P&gt;GIS is all about bringing information of all types together into one place in order to see patterns, correlations, and more.&amp;nbsp; So it is critical for products to be able to handle multiple credentials and keep them all straight.&amp;nbsp; In addition there has been a big push for more one stop shops for users.&amp;nbsp; They get lost having to go to a dozen different websites to get the info they need.&amp;nbsp; Instead we need to collect up all the info they need and present them together to get the full picture.&lt;/P&gt;&lt;P&gt;Thank you&lt;/P&gt;</description>
      <pubDate>Thu, 19 Feb 2026 14:32:01 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-experience-builder-ideas/streamlining-authentication-between-arcgis-online/idc-p/1685165#M5037</guid>
      <dc:creator>DougBrowning</dc:creator>
      <dc:date>2026-02-19T14:32:01Z</dc:date>
    </item>
    <item>
      <title>Re: Streamlining authentication between ArcGIS Online and Portal to support embedded content</title>
      <link>https://community.esri.com/t5/arcgis-experience-builder-ideas/streamlining-authentication-between-arcgis-online/idc-p/1696277#M5275</link>
      <description>&lt;P&gt;We just discovered this yesterday. This was a disappointment as we are taking advantage of the functionality in AGOL that Portal does not have. Thank you for submitting this.&lt;/P&gt;</description>
      <pubDate>Tue, 14 Apr 2026 21:01:37 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-experience-builder-ideas/streamlining-authentication-between-arcgis-online/idc-p/1696277#M5275</guid>
      <dc:creator>ShoNuff</dc:creator>
      <dc:date>2026-04-14T21:01:37Z</dc:date>
    </item>
  </channel>
</rss>

