<?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>topic AuthNet Hosted iFrame broken for VPN users in Chrome 142+ in Integration and Testing</title>
    <link>https://community.developer.cybersource.com/t5/Integration-and-Testing/AuthNet-Hosted-iFrame-broken-for-VPN-users-in-Chrome-142/m-p/95171#M58791</link>
    <description>&lt;P&gt;We are finding that users on a VPN (or anyone on a private network) are unable to use the Hosted Authnet iFrame on our site.&amp;nbsp;We are specifically using the iframe delivered from `/customer/addPayment`. I know Chrome 142 tightened enforcement of the Local Network Access spec, blocking cross-origin requests to private networks, and we haven't been able to figure out how to work around it yet.&lt;/P&gt;&lt;P&gt;We have added the `allow="local-network-access"` permission attribute to the iframe on our end, as well as updated CORS settings on our side, but we find it's insufficient without the corresponding server-side header. The missing piece appears to be on the AuthNet side: `Access-Control-Allow-Private-Network: true`.&lt;/P&gt;&lt;P&gt;Is there something we're missing to restore full functionality for these users on VPNs, or do we need an update from AuthNet?&lt;/P&gt;</description>
    <pubDate>Thu, 30 Apr 2026 14:02:45 GMT</pubDate>
    <dc:creator>prlcasey</dc:creator>
    <dc:date>2026-04-30T14:02:45Z</dc:date>
    <item>
      <title>AuthNet Hosted iFrame broken for VPN users in Chrome 142+</title>
      <link>https://community.developer.cybersource.com/t5/Integration-and-Testing/AuthNet-Hosted-iFrame-broken-for-VPN-users-in-Chrome-142/m-p/95171#M58791</link>
      <description>&lt;P&gt;We are finding that users on a VPN (or anyone on a private network) are unable to use the Hosted Authnet iFrame on our site.&amp;nbsp;We are specifically using the iframe delivered from `/customer/addPayment`. I know Chrome 142 tightened enforcement of the Local Network Access spec, blocking cross-origin requests to private networks, and we haven't been able to figure out how to work around it yet.&lt;/P&gt;&lt;P&gt;We have added the `allow="local-network-access"` permission attribute to the iframe on our end, as well as updated CORS settings on our side, but we find it's insufficient without the corresponding server-side header. The missing piece appears to be on the AuthNet side: `Access-Control-Allow-Private-Network: true`.&lt;/P&gt;&lt;P&gt;Is there something we're missing to restore full functionality for these users on VPNs, or do we need an update from AuthNet?&lt;/P&gt;</description>
      <pubDate>Thu, 30 Apr 2026 14:02:45 GMT</pubDate>
      <guid>https://community.developer.cybersource.com/t5/Integration-and-Testing/AuthNet-Hosted-iFrame-broken-for-VPN-users-in-Chrome-142/m-p/95171#M58791</guid>
      <dc:creator>prlcasey</dc:creator>
      <dc:date>2026-04-30T14:02:45Z</dc:date>
    </item>
  </channel>
</rss>

