<?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 Re: Microform V2 Integration - CSP Frame-Ancestors issue , Sandbox environment in cybersource APIs</title>
    <link>https://community.developer.cybersource.com/t5/cybersource-APIs/Microform-V2-Integration-CSP-Frame-Ancestors-issue-Sandbox/m-p/91453#M2174</link>
    <description>&lt;P&gt;Seems it was related to the TargetOrgins[] passed over in the initial Capture Context. For now - Hard-coded to our SF VF Page url and seems to resolve all this confusion.&lt;/P&gt;</description>
    <pubDate>Wed, 19 Mar 2025 17:42:12 GMT</pubDate>
    <dc:creator>mdennis</dc:creator>
    <dc:date>2025-03-19T17:42:12Z</dc:date>
    <item>
      <title>Microform V2 Integration - CSP Frame-Ancestors issue , Sandbox environment</title>
      <link>https://community.developer.cybersource.com/t5/cybersource-APIs/Microform-V2-Integration-CSP-Frame-Ancestors-issue-Sandbox/m-p/91452#M2173</link>
      <description>&lt;P&gt;Hello,&lt;BR /&gt;&lt;BR /&gt;I've reached a speedbump in our upgrade from Flex Microform v0.4 to v2. After loading the Flex script, and mounting the CardNumber and CVV fields, we get a nasty CSP error from Cybersource, related to the mounted iframe.&lt;BR /&gt;&lt;BR /&gt;&lt;FONT face="courier new,courier"&gt;&lt;STRONG&gt;Content-Security-Policy: The page’s settings blocked the loading of a resource (frame-ancestors) at &amp;lt;unknown&amp;gt; because it violates the following directive: “frame-ancestors &lt;/STRONG&gt;&lt;/FONT&gt;&lt;A href="https://cybersource.com”" target="_blank" rel="noopener"&gt;&lt;FONT face="courier new,courier"&gt;&lt;STRONG&gt;https://cybersource.com”&lt;/STRONG&gt;&lt;/FONT&gt;&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;This is being implemented in a LWC/VF Page in Salesforce sandbox. It's my understanding that there’s nothing in Salesforce (or in our Visualforce/LWC code) that can override a &lt;STRONG&gt;third‑party iframe’s&lt;/STRONG&gt; frame‑ancestors policy — that directive is sent by CyberSource’s servers and enforced by the browser. Is it true CyberSource has to whitelist our exact Salesforce origin in their frame‑ancestors CSP header?&lt;BR /&gt;&lt;BR /&gt;Why is this not mentioned anywhere in the documentation. Any one else encountered this before?&lt;BR /&gt;&lt;BR /&gt;These are the response headers coming back from testflex.cybersource.com:&lt;BR /&gt;&lt;BR /&gt;&lt;FONT face="courier new,courier"&gt;&lt;STRONG&gt;HTTP/2 200 &lt;/STRONG&gt;&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT face="courier new,courier"&gt;&lt;STRONG&gt;date: Wed, 19 Mar 2025 17:05:43 GMT&lt;/STRONG&gt;&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT face="courier new,courier"&gt;&lt;STRONG&gt;content-type: text/html;charset=utf-8&lt;/STRONG&gt;&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT face="courier new,courier"&gt;&lt;STRONG&gt;content-security-policy: frame-ancestors &lt;A href="https://cybersource.com" target="_blank" rel="noopener"&gt;https://cybersource.com&lt;/A&gt;; default-src 'self'; connect-src 'self'; script-src 'self'; style-src 'unsafe-inline'; child-src 'none'; frame-src 'none'; img-src 'none'; font-src 'none'; media-src 'none'; object-src 'none'; report-uri /cybersource/microform/v1/violation-report;&lt;/STRONG&gt;&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT face="courier new,courier"&gt;&lt;STRONG&gt;x-content-type-options: nosniff&lt;/STRONG&gt;&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT face="courier new,courier"&gt;&lt;STRONG&gt;cache-control: no-store&lt;/STRONG&gt;&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT face="courier new,courier"&gt;&lt;STRONG&gt;expires: Thu, 01 Jan 1970 00:00:00 GMT&lt;/STRONG&gt;&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT face="courier new,courier"&gt;&lt;STRONG&gt;strict-transport-security: max-age=31536000&lt;/STRONG&gt;&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT face="courier new,courier"&gt;&lt;STRONG&gt;v-c-correlation-id: a3c7123b-a2c1-4d62-a27c-82fd18c90d62&lt;/STRONG&gt;&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT face="courier new,courier"&gt;&lt;STRONG&gt;x-opnet-transaction-trace: e682e054-d852-450a-b102-f23c7fba80da-22769-8892031&lt;/STRONG&gt;&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT face="courier new,courier"&gt;&lt;STRONG&gt;cf-cache-status: DYNAMIC&lt;/STRONG&gt;&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT face="courier new,courier"&gt;&lt;STRONG&gt;server: cloudflare&lt;/STRONG&gt;&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT face="courier new,courier"&gt;&lt;STRONG&gt;cf-ray: 922e8e690995b7f2-MIA&lt;/STRONG&gt;&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT face="courier new,courier"&gt;&lt;STRONG&gt;content-encoding: br&lt;/STRONG&gt;&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT face="courier new,courier"&gt;&lt;STRONG&gt;X-Firefox-Spdy: h2&lt;/STRONG&gt;&lt;/FONT&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 19 Mar 2025 17:14:58 GMT</pubDate>
      <guid>https://community.developer.cybersource.com/t5/cybersource-APIs/Microform-V2-Integration-CSP-Frame-Ancestors-issue-Sandbox/m-p/91452#M2173</guid>
      <dc:creator>mdennis</dc:creator>
      <dc:date>2025-03-19T17:14:58Z</dc:date>
    </item>
    <item>
      <title>Re: Microform V2 Integration - CSP Frame-Ancestors issue , Sandbox environment</title>
      <link>https://community.developer.cybersource.com/t5/cybersource-APIs/Microform-V2-Integration-CSP-Frame-Ancestors-issue-Sandbox/m-p/91453#M2174</link>
      <description>&lt;P&gt;Seems it was related to the TargetOrgins[] passed over in the initial Capture Context. For now - Hard-coded to our SF VF Page url and seems to resolve all this confusion.&lt;/P&gt;</description>
      <pubDate>Wed, 19 Mar 2025 17:42:12 GMT</pubDate>
      <guid>https://community.developer.cybersource.com/t5/cybersource-APIs/Microform-V2-Integration-CSP-Frame-Ancestors-issue-Sandbox/m-p/91453#M2174</guid>
      <dc:creator>mdennis</dc:creator>
      <dc:date>2025-03-19T17:42:12Z</dc:date>
    </item>
  </channel>
</rss>

