Starting March 3rd, 2021, all new Flex applications are required to register their valid URLs under Twilio Flex's Allowed URLs list in order to embed Flex as an iframe. Existing Flex applications have until May 3, 2021 to confirm their registered URLs.
Our security policy will help guard against cross-site scripting (XSS) and other content injection attacks, such as click-jacking. Instead of blindly trusting everything that a server delivers, we have implemented a policy that lets you add a list of sources of trusted content. Your allowed URL(s) will be added to a CSP header as a valid frame-ancestor, along with a
report-uri directive on authenticated Flex requests. This tells your browser to report an error when unregistered URLs are attempting to iframe
These instructions only apply to our hosted
This is enabled by default for all new Flex applications. If you need to add more URL(s) to your Allowed URLs list, review the URL Registration Rules.
We have prepopulated the allowed URLs list for you based on your application activity. Review and confirm that they are the right URL(s). In order to test the policy on your account, toggle "Enable CSP", click Save, and refresh your external application.
You should be able to log into your Flex application if the external URL has been registered correctly. Note that unauthenticated requests are redirected to the Flex login page.
Keep in mind that the ability to enable and disable CSP via the toggle is available to all pre-existing Flex applications until the day the policy is enforced.
When adding your Allowed URL(s) list, keep the following rules in mind:
||Full URLs are required, without any trailing slashes. For local development, register
||Wildcards are not supported|
||URL paths are not supported|