I received this email today. I don't understand it, but assume it applies to C&P. Do you know what we need to do, or will you be issuing an update that takes care of this. PDF of email is too big to attach, but here are two key paragraphs.
In September, we contacted you to make you aware that Salesforce is making the Enforce CORS Allowlist for Lightning Apps release update available to enhance your org’s security. This update gets enforced with the Spring ‘22 release, when your org’s ability to reference Salesforce assets from another domain can be affected if the domains aren’t added to the Cross-Origin Resource Sharing (CORS) allowlist.
You’re being contacted about this change because your org has one or more external domains calling on your Salesforce resources that are affected by this change. Read on for more information about the change and how to prepare today to avoid impact before the Spring ‘22 release.
Thanks - kate
In September, we contacted you to make you aware that Salesforce is making the Enforce CORS Allowlist for Lightning Apps release update available to enhance your org’s security. This update gets enforced with the Spring ‘22 release, when your org’s ability to reference Salesforce assets from another domain can be affected if the domains aren’t added to the Cross-Origin Resource Sharing (CORS) allowlist.
You’re being contacted about this change because your org has one or more external domains calling on your Salesforce resources that are affected by this change. Read on for more information about the change and how to prepare today to avoid impact before the Spring ‘22 release.
Thanks - kate
Comment