What is the default method of authentication for signed requests in Salesforce?

The default method of authentication for signed requests in Salesforce is based on the concept of ensuring trust and verification between different systems. It utilizes the credentials provided while setting up the integration, emphasizing reliability and security.

In Salesforce, signed requests are often used to confirm the identity of the sender by including a signature based on a secret key or token. This allows the receiving system to validate the authenticity of the request, ensuring that it originates from a legitimate source. While other methods like OAuth are widely recognized for authentication purposes, signed requests primarily rely on the integrity of the message through signature verification, which solidifies the idea of a default authentication method centered around signed requests.

This method is intrinsic to Salesforce's approach to maintaining trust in integrations, where the key focus is on establishing secure connections without necessarily defaulting to more complex authentication flows unless specified otherwise in the integration setup. Understanding this foundational aspect of authentication in Salesforce integrations is essential for architects working on connecting Salesforce with various external systems.