Salesforce Lightning Aura Components Enabled
Last updated
Was this helpful?
Last updated
Was this helpful?
Salesforce Experience (or Community) Cloud is a Customer Relationship Management (CRM) platform often used by software companies and organizations to manage their customer relationships, share information & collaborate with their employees and customers (documentation, knowledge bases, help articles, etc.), to provide support using support ticketing and much more.
It's a public-facing platform and thereby also indexed by popular search engines like Google and Bing.
Salesforce Communities (Experience Cloud) is built upon the . This framework has a set of reusable components to help developers, admins, and IT teams easily create web and mobile applications.
Salesforce Lightning consists of , these components are self-contained and reusable allowing developers to speed up the development of their projects.
The framework already comes with pre-built base components that developers and admins can use but Salesforce Lightning also provides the option to create your custom components using Salesforce's strongly typed programming language, .
A custom component can be defined to view or modify data in Salesforce. However, properly enforcing role-based permissions, and adhering to the "Least-privilege" principle often proves to be difficult for inexperienced users as it can get complex rapidly.
A misconfigured custom component can lead to a wide variety of security vulnerabilities, from excessive data leaks (often including personally identifiable information, or PII) to horizontal/vertical privilege escalation.
Replicate the following POST HTTP request to verify that the Aura API endpoint is enabled for Guest profile (unauthenticated visitors):
The endpoint should respond with a 401 Unauthorized status code indicating an invalid session error (aura:invalidSession):
If the HTTP request above returned a 404 status code, try requesting one of the following API endpoints:
The target instance can also be pointed to one of the following FQDNs:
Salesforce Lightning employs a role-based security model and essentially allows admins to configure security access controls on CRUD operations at three separate levels: the Object (database), Field (column), and Record (data entry) levels.
Revising the current options for each (custom) profile and adhering to the principle of least privilege is essential.
On your Salesforce Lightning instance, you can navigate to /lightning/setup/Profiles/home to view all the profiles.
Select a profile and revise each enabled permission individually. Make changes to the profiles accordingly.
Make sure to save your changes at the end.
Do not only set permissions for Guest (unauthenticated) visitors. A common mistake admins make is only enforcing access controls for non-authenticated users when it is possible for any visitor to sign up for an account.
It is also strongly recommended to turn off API access to Guest (unauthenticated) visitors.
When insufficient access controls are enforced on Salesforce Lightning, unauthorized users may retrieve sensitive data, perform unwanted actions, and/or even escalate their current privileges.
Revising all access controls and preventing unauthorized users from viewing or performing actions beyond what is required in their scope or role is necessary.
