|
| 1 | +--- |
| 2 | +updated: 2021-03-09 |
| 3 | +category: 🔐 Zero Trust |
| 4 | +difficulty: Intermediate |
| 5 | +--- |
| 6 | + |
| 7 | +# Salesforce with Access for SaaS configuration |
| 8 | + |
| 9 | +**🗺️ This tutorial covers how to:** |
| 10 | +* Configure Salesforce as a SaaS application in Teams |
| 11 | +* Force logins to Salesforce through Cloudflare's Zero Trust rules |
| 12 | + |
| 13 | +**⏲️ Time to complete: 15 minutes** |
| 14 | + |
| 15 | +What's needed to complete this guide: |
| 16 | +* Admin access to a Cloudflare for Teams account |
| 17 | +* Admin access to a Salesforce account |
| 18 | + |
| 19 | +## Set up Salesforce as a SaaS application in Teams |
| 20 | + |
| 21 | +1. On the [Teams dashboard](https://dash.teams.cloudflare.com), navigate to **Access > Applications**. |
| 22 | +1. Select the SaaS application type. |
| 23 | +1. Next, select *Salesforce* from the **Application** drop-down menu. |
| 24 | +1. Fill the remaining fields as follows: |
| 25 | + * **Entity ID**: `https://salesforce.com` |
| 26 | + * **Assertion consumer service URL**: https://[YOUR_SFDC_DOMAIN].my.salesforce.com |
| 27 | + * **Name ID format**: Email |
| 28 | +1. Click **Next**. |
| 29 | +1. Set the desired policy configuration for user access. |
| 30 | +1. Click Add application. |
| 31 | +1. Next, take note of the **SSO endpoint**, the **Access Entity ID or Issuer**, and the **Public Key**. |
| 32 | + |
| 33 | + |
| 34 | + |
| 35 | +## Create a certificate file |
| 36 | + |
| 37 | +1. Paste the **Public key** in VIM or another code editor. |
| 38 | +1. Wrap the certificate in `-----BEGIN CERTIFICATE-----` and `-----END CERTIFICATE-----`. |
| 39 | +1. Set the file extension as `.crt` and save. |
| 40 | + |
| 41 | + |
| 42 | +## Enable Single Sign-On in Salesforce |
| 43 | + |
| 44 | +1. In Salesforce, ensure your users have **Federation IDs**. |
| 45 | + |
| 46 | + <Aside> |
| 47 | + The Federation ID is found under Manage Users > Users in Setup. The Federation ID should match the email address of the user authenticating via Access. |
| 48 | + </Aside> |
| 49 | + |
| 50 | +  |
| 51 | + |
| 52 | +2. Navigate to **Security Controls > Single Sign-On Settings** |
| 53 | +3. Set the following global settings: |
| 54 | + * **SAML Enabled:** true |
| 55 | + * **Make federation ID case-insensitive:** true |
| 56 | + |
| 57 | + |
| 58 | + |
| 59 | +## Create a new SAML Single-Sign On configuration |
| 60 | + |
| 61 | +1. Create a new SAML Single-Sign On configuration |
| 62 | +Configure as follows: |
| 63 | + * **Name:** (this is what you want your users to see on sign in) |
| 64 | + * **API name:** (this will pre-populate) |
| 65 | + * **Issuer:** your-team-name.cloudflareaccess.com, where your-team-name is your [team name](/glossary#team-name). |
| 66 | + * **Identity Provider Certificate**: upload the `.crt` certificate file you’ve created in the previous step. |
| 67 | + * **EntityID**: `https://salesforce.com` |
| 68 | + * **SAML Identity type:** Assertion contains the Federation ID from the User object |
| 69 | + * **Identity Provider Login URL**: This is the SSO endpoint provided in the Teams dashboard for that application. |
| 70 | + |
| 71 | +1. Click **Save**. |
| 72 | + |
| 73 | +  |
0 commit comments