Restrict Access to @AuraEnabled Apex Methods for Guest and Portal Users Based on User Profile (Critical Update, Postponed)
Where: This change applies to Aura components, Lightning web components, and flows in Lightning communities, portals, and Salesforce Sites.
When: This critical update is enforced when a sandbox or production org is upgraded to Winter ’21. Enforcement starts on August 9, 2020 and takes effect when your instance is upgraded to Winter ’21. To find the exact activation date for your instance, refer to https://status.salesforce.com.
Why: When this critical update is activated, a guest, portal, or community user can access an @AuraEnabled Apex method only when the user’s profile or a permission set allows access to the Apex class. This critical update enforces user profile and permission set restrictions for Apex classes used by Aura and Lightning web components.
How: To test this critical update, we recommend working in a sandbox to complete testing before the initial enforcement date of August 9, 2020, which is the Auto-Activation Date in the UI. After August 9, you can no longer activate or deactivate the critical update and you can test behavior only in a sandbox that’s already been upgraded to Winter ’21. If you don’t activate the critical update before May 7, it will be automatically activated when your instance is upgraded to Winter ’21.
- From Setup, enter Critical Updates in the Quick Find box.
- Select Critical Updates.
- Review the details for the “Restrict Access to @AuraEnabled Apex Methods for Guest and Portal Users Based on User Profile” critical update.
- Click Activate.
- Test that custom Aura components, Lightning web components, and flows that you’ve developed are working correctly for guest, portal, and community users.