Hi everyone,
I am trying to embed an Ignition WebDev Python Resource (HTML) into Power BI Desktop using the HTML Content visual. Currently, the content is being blocked because the response header X-Frame-Options is set to SAMEORIGIN.
I have attempted to remove this header and set the CSP by modifying ignition.conf, but the Gateway seems to completely ignore these parameters.
What I have configured in ignition.conf: I added the following lines to the wrapper.java.additional section. I ensured the numbering is continuous (my previous line is .9) and there are no commenting # characters at the start.
wrapper.java.additional.9=-Dedition=
wrapper.java.additional.10=-Dignition.http.header.X-Frame-Options=
wrapper.java.additional.11=-Dignition.http.header.Content-Security-Policy="frame-ancestors *"
Troubleshooting Steps Taken:
-
Restarted Gateway: I performed a hard restart via Windows
services.msc(Restart Service). I also tried usingstop.batandstart.batwith Admin privileges. -
Verified Syntax: Checked for hidden spaces, confirmed no
#signs, and verified the numbering sequence is unbroken. -
Checked Browser: After restart, Chrome DevTools (Network tab) still shows
X-Frame-Options: SAMEORIGIN. -
Checked
wrapper.log(CRITICAL ISSUE): I inspected thewrapper.logafter the restart. I can see other parameters being loaded, but the lines forX-Frame-OptionsandContent-Security-Policyare completely missing from the log. It seems the wrapper is not reading these specific lines at all.
My Question: Why would the Ignition Gateway (or Java Wrapper) ignore valid wrapper.java.additional parameters in the config file? Is there a Windows permission issue (like VirtualStore) or a caching mechanism that prevents ignition.conf changes from being picked up even after a service restart?
Any help would be appreciated. I've been stuck on this for days!
Thanks.