Hello everyone, I am currently working on an external service integration inside Liferay DXP 7.4 where we need to allow regional users to verify their utility account details directly within a custom portal widget. We are referencing the multi-step verification approach described in this guide for fetching customer bill duplicates and reference numbers. While testing the integration inside our portal page, we noticed that Senna.js single-page application navigation causes the external frame state to reset unexpectedly whenever a user navigates between portal tabs. On top of that, strict Content Security Policy directives in our Liferay environment are throwing frame-src and CORS console warnings during the asynchronous lookup. Has anyone encountered similar SPA caching or CSP conflicts when embedding third-party utility lookup workflows into Liferay portlets, and what would be the recommended architecture to handle cross-origin framing without weakening portal security?