Salesforce Integration

Salesforce Integration Direction

Integration can be two direction inbound integration or outbound Integration

1) Inbound Integration :

An external System initiates contact with Salesforce

2) Outbound Integration :

Salesforce initiates contact with an external system

What is API

API stands for Application Programming Interface. It is the means that allows two applications to talk to each other.There are following type of API in Salesforce : 1) REST API 2) SOAP API 3) Bulk API

REST API

Salesforce REST API is a powerful web service that allows external applications to interact with Salesforce data using standard HTTP methods such as GET, POST, PUT, DELETE. It is lightweight and commonly used for web and mobile applications.

Key Features of REST API in Salesforce

Stateless

Each request is independent; no session is maintained.

Supports JSON & XML

Preferred format is JSON for easy parsing.

Uses Standard HTTP Methods –
1. 1. GET → Retrieve records
  2. POST → Create records
  3. PUT → Update records
  4. DELETE → Remove records
OAuth Authentication

Uses OAuth 2.0 for secure access.

Scalability

Best for real-time integration between Salesforce and external applications.

Common REST API Endpoints

Example: Calling REST API in Salesforce (Using cURL)

Get Account Details:

curl -X GET https://yourInstance.salesforce.com/services/data/v59.0/sobjects/Account/0015g00000ABC123

-H "Authorization: Bearer ACCESS_TOKEN"

-H "Content-Type: application/json"

Create a New Contact:

curl -X POST https://yourInstance.salesforce.com/services/data/v59.0/sobjects/Contact/

-H "Authorization: Bearer ACCESS_TOKEN"

-H "Content-Type: application/json"

-d '{

"FirstName": "John",

"LastName": "Doe",

"Email": "john.doe@example.com"

}'

How to Authenticate REST API Requests?

Salesforce REST API requires authentication via OAuth 2.0, using one of these methods:

Username-Password Flow
Authorization Code Flow
JWT (JSON Web Token) Flow
Client Credentials Flow

What is Connected App

A Connected App in Salesforce is a framework that allows external applications to integrate with Salesforce,using APIs and standard authentication protocols. Connected Apps are essential for securely connecting external systems,like mobile apps, web applications, and third-party services, to Salesforce for data exchange and service consumption.
Key Components of a Connected App

1. Client ID and Client Secret:

These are credentials used by the external application to authenticate itself with Salesforce.The Client ID (or Consumer Key) uniquely identifies the app and theClient Secret (or Consumer Secret) is used to authenticate the app securely.

2. OAuth Scopes

These define the level of access that the app will have to Salesforce data.For example, you can specify scopes to allow read-only access,full access, or access only to specific APIs(like Chatter, REST, or custom scopes).

3. Callback URL (Redirect URI)

This is the endpoint in the external application where Salesforce will redirect the userafter they authenticate.It’s used during the OAuth authentication flow to complete the login process.

4. Permissions

You can configure additional security settings like IP restrictions, session settings,and token policies to control how the connected app can access Salesforce.

5. Authentication Protocols

Connected Apps support multiple authentication protocols, such as:OAuth 2.0 : A widely used protocol for secure authorization.SAML : Often used in Single Sign-On (SSO) scenarios.JWT (JSON Web Token): Used for server-to-server integrations without user interaction.

Common Use Cases for Connected Apps

Integrating with External Systems:

External systems like ERP systems, marketing tools, and analytics platforms often need to pull or push data to and from Salesforce.

Mobile Applications:

Mobile apps that need to access Salesforce data can use a connected app to authenticate users and retrieve data securely.

Third-Party App Integrations:

Many third-party applications in the Salesforce AppExchange use connected apps to securely connect to Salesforce Orgs.

Single Sign-On (SSO):

You can configure a connected app to work with SAML or OAuth-based SSO, allowing users to log in to external systems using their Salesforce credentials.

How to Set Up a Connected App

1. Go to Setup → App Manager in Salesforce. 2. Click New Connected App. 3. Fill in the basic details (like App Name and Contact Email). 4. In API (Enable OAuth Settings), check Enable OAuth Settings. 5. Configure Callback URL, OAuth Scopes, and other settings as needed. 6. Save the app and obtain the Client ID and Client Secret from the app’s details page.

Authentication Flows Supported by Connected Apps

Connected Apps support various OAuth flows, including: 1. Authorization Code Flow: Used for apps that access Salesforce on behalf of a user. 2. Implicit Grant Flow: Often used by single-page apps that need access tokens directly. 3. Client Credentials Flow: Used for server-to-server integrations without user interaction. 4.JWT Bearer Token Flow: Allows integrations using JSON Web Tokens without user interaction.

Security and Policies

Benefits of Connected Apps

IP Restrictions:

Restrict access to certain IP addresses.

Session Policies:

Control session duration and refresh policies.

Permission Sets:

Assign permission sets to users who need access to the connected app, adding an additional layer of security.

Secure Data Access

Ensures secure data exchange between Salesforce and external systems.Flexible Authentication: Supports multiple authentication methods for different scenarios.

User Consent

Requires users to grant permission, improving transparency and security.

Enhanced Control

Provides admins with control over which apps and users can access Salesforce data.

Auth Providers

An Auth Provider (Authorization Provider) in Salesforce is a configuration that enables Salesforce to integrate with external identity providers (IdPs) for authentication and Single Sign-On (SSO). It is commonly used in cases where you want Salesforce users to authenticate through an external system or connect to third-party services using standards like OAuth, OpenID Connect, and SAML.

Key Components of an Auth Provider

1. Provider Type: The type of external identity provider. Salesforce provides built-in options like: • Facebook • Google • LinkedIn • GitHub • OpenID Connect (for custom providers) • SAML • Salesforce ( to connect multiple Salesforce orgs ) 2. Consumer Key and Consumer Secret: Also known as the Client ID and Client Secret in OAuth. These are obtained from the identity provider and are used to authenticate Salesforce with the external service. 3. Authorize Endpoint URL: The URL that Salesforce uses to request authorization from the external provider. 4. Token Endpoint URL: The URL that Salesforce uses to obtain an access token after the authorization is granted. 5. Redirect URI (Callback URL): The URL Salesforce redirects users to after successful authentication. This URL must be configured in the external identity provider. 6. Scopes: Scopes define the level of access that Salesforce will request from the identity provider. For example, scopes could allow access to a user’s profile information, email, or other data. 7. Custom Error URL: An optional URL to redirect users in case of authentication errors

Common Use Cases for Auth Provider

1. Single Sign-On (SSO) for Users: Allows Salesforce users to authenticate using an external identity provider, enabling a seamless login experience with SSO. 2. Social Sign-On: Enables users to log in to Salesforce Communities using social identities, like Google, Facebook, or LinkedIn accounts. 3. Third-Party API Integrations: When Salesforce needs to interact with an external API on behalf of a user, an Auth Provider can be configured to facilitate the OAuth flow. 4. Multi-Org Authentication: Allows one Salesforce org to authenticate with another Salesforce org, which can be helpful for organizations with multiple Salesforce environments.

How to Set Up an Auth Provider in Salesforce

1. Go to Setup in Salesforce. 2. Search for and go to Auth. Providers under Security. 3. Click New to create a new Auth Provider. 4. Choose the Provider Type (e.g., Google, Facebook, LinkedIn, OpenID Connect, or Salesforce). 5. Enter the required fields, including: • Consumer Key and Consumer Secret • Authorize Endpoint URL • Token Endpoint URL • Default Scopes • Callback URL (which Salesforce generates automatically after you save the provider) 6. Save the configuration. 7. After saving, use the Callback URL generated by Salesforce. You’ll need to add this URL to the identity provider’s configuration as an authorized redirect URI.

Benefits of Using Auth Providers

• Enhanced Security: By delegating authentication to a trusted identity provider, you can ensure secure access to Salesforce. • Improved User Experience: Simplifies the login process for users with SSO, allowing them to use existing credentials. • Customizable Access: Enables control over data access levels through scopes. • Standardized Protocols: Supports OAuth, OpenID Connect, and SAML, which are widely accepted authentication protocols.

Differences Between Auth Provider and Connected App

• Auth Provider: Used to authenticate Salesforce against external identity providers and enable SSO for users. It’s primarily for setting up the login experience or connecting to third-party services. • Connected App: Primarily used for integrating external applications with Salesforce, enabling them to access Salesforce data through APIs.

Salesforce Integration