• Home
• App Integrations
• Single Sign-On Integrations
• Salesforce Community Single Sign-On

Salesforce Community Single Sign-on (SAML SSO)

---

Salesforce Community has made mandatory for all users to use MFA for their login -
Click Here to know more on Salesforce Community MFA policy.

Salesforce Community SSO or Salesforce Community Single Sign On solution by miniOrange allows all system users to access all authorised system resources with a single username and password, rather than having separate usernames and passwords for each resource on the network. Salesforce Community is a cloud-based software firm situated in San Francisco, California, United States. It offers CRM services as well as enterprise applications for customer service, marketing automation, analytics, and application development.

miniOrange SSO Solution for Salesforce Community helps you Login into your Salesforce Community application with same credentials being used for various applications. miniOrange helps you to use one federated identity to connect will all your applications along with your Salesforce Community CRM application using their Salesforce Community SSO solution. miniOrange Cloud and On-Premise solution is easy to setup. miniOrange also provides Multi-factor authentication on top of SSO with your Salesforce Community Login with 15+ MFA methods.

Single Sign-on supported editions:

Federated Authentication	All Saleforce org editions
Delegated Authentication	Professional, Enterprise, Performance, Unlimited, Developer, and Database.com Editions
Authentication Providers	Professional, Enterprise, Performance, Unlimited, and Developer Editions

Following are the required user permissions for Salesforce Community org Single Sign-on:

View SSO settings	View Setup and Configuration
Edit and Modify SSO settings	"Customize Application" and "Modify All Data"

You can configure Salesforce Community Single sign-on (SSO) to authenticate your users in following features :

• Salesforce Community as Service Provider (SP)

Setup single sign-on (SSO) for Salesforce Community so that your end users can log in to Salesforce Community with single set of credentials from any identity provider or external directory. In this scenario, the admin can setup an identity provider using Security Assertion Markup Language (SAML). You can also use Active directory (AD) or any database as Identity source.



• Salesforce Community as an Identity Provider (IdP)

Setup single sign-on (SSO) so that your employees or members log in to any other application or any external service provider using Salesforce Community credentials. With this system, your Salesforce Community account will act as a SAML identity provider and integrate with the other applications or service providers.



• Salesforce Community as both Service Provider (SP) and Identity Provider (IdP)

Salesforce Community can act as SP and IdP both based on the use case and type of authentication required. You can login into multiple Salesforce Community orgs using credentials of other org or login to your Salesforce Community org using any Identity source. SSO can be set up and configured between multiple Salesforce Community orgs to have seamless and secure acess and data security.



• Single Logout feature

With this feature, you will be automatically logged out of all the applications that are connected with Idneity provider (IdP) when you log out from Salesforce Community org or any other app.



• Mandate users to Login using SSO

Single Sign-on can make it mandatory for all users to log in using SSO. This will prevent any users from login using any other source and bypassing the login system. No users will be able to have direct login making it a streamline and secure process.

miniOrange system for Salesforce Community Single Sign-On or Salesforce Community SSO integration supports the following flows:

• SP (Service Provider) Initiated Single Sign-On (SSO)

In this flow, the user tries to login to the Serivce Provider (Salesforce Community) directly. The request is redirected to the Identity Provider for authentication. On sucessfull authentication from the Identity provider, the user is given access to the application.



• IdP (Identity Provider) Initiated Single Sign-On (SSO)

In this flow, the user logs in to the Identity Provider using his credentials. Now the user can access any of the configured Service Providers (salesforce community, etc.) through the Identity Provider Dashboard without having to enter the credentials agian.

(Note - In order to do SP initiated SSO into Salesforce Community, you need to create a custom Domain. Check this link - Salesfoce domain changes and follow the below steps)

• Login to your Salesforce Community account.
• Go to Setup in the top-right section of page.



• Now in the left pane, select Domain Management.
• Select My Domain.
• Choose your domain name, check for availability and if available, proceed by clicking the Register Domain button.



• Test your domain once it is ready, by clicking the link and then click Deploy to Users.
• Search for Company Information in the search bar.
• Copy Organization Id. (This will be required later)

Follow the Step-by-Step Guide given below for Salesforce Community Single Sign-On (SSO)

1. Configure Salesforce Community in miniOrange

• Login into miniOrange Admin Console.
• Go to Apps and click on Add Application button.



• In Choose Application Type click on SAML/WS-FED application type.



• Search for Salesforce Community in the list, if you don't find Salesforce Community in the list then, search for custom and you can set up your application via Custom SAML App.

• Enter the following values in the respective fields.



Application Name	Salesforce Community
SP Entity ID or Issuer	https://[yourdomain].my.salesforce.com/?so=[organization_id]
ACS URL	https://[yourdomain].my.salesforce.com/?so=[organization_id]
Single Logout URL	https://customdomain.my.salesforce.com
Sign Response	ON





• Click Next, now in the Attribute Mapping add and configure the attributes.



• Click on Save.
• Your application is saved successfully. Now click on the Select button against your newly created application. Go to Metadata.



• On the Metadata page, click on Show Metadata Details and choose either of the two Metadata options :
• If you want to use miniOrange as User-Store i.e., your user identities will be stored in miniOrange then download the metadata file under the heading 'INFORMATION REQUIRED TO SET MINIORANGE AS IDP'.
• If you want to authenticate your users via any external Identity Provider (IDP) like Active Directory, Okta, OneLogin, Google, Apple ID, etc then download the Metadata file under the heading 'INFORMATION REQUIRED TO AUTHENTICATE VIA EXTERNAL IDPS'.



• Then click on Download Metadata.

2. Configure SSO for Salesforce Community Site

1. Pre-requisite: You need to configure SSO for Salesforce Community using the Salesforce.com application in miniOrange. Click Here for more details.
2. Copy the Issuer & Entity ID from the Salesforce.com app setup instructions.
1. Navigate to Admin > Applications > Select Salesforce.com
2. Click Sign on tab.
3. Click View Setup Instructions. Copy the Issuer & Entity ID values.
3. Copy the Community Site SSO login URL.
1. Log into your Salesforce Community instance as an Admin.
2. Navigate to Security Controls > Single Sign-On Settings.
3. Select the name of the SSO configuration created for the Saleforce.com application.
4. Scroll down and expand the For Communities option. Copy the Single Sign on URL.

3. Test SSO Configuration

Test SSO login to your Salesforce Community account with miniOrange IdP:

Using SP Initiated Login

• Go to your Salesforce Community URL, here you will be either asked to enter the username or click on the SSO link which will redirect you to miniOrange IdP Sign On Page.



• Enter your miniOrange login credential and click on Login. You will be automatically logged in to your Salesforce Community account.

Using IDP Initiated Login

• Login to miniOrange IdP using your credentials.



• On the Dashboard, click on Salesforce Community application which you have added, to verify SSO configuration.





Not able to configure or test SSO?


Contact us or email us at idpsupport@xecurify.com and we'll help you setting it up in no time.

4. Configure Your User Directory (Optional)

miniOrange provides user authentication from various external sources, which can be Directories (like ADFS, Microsoft Active Directory, Azure AD, OpenLDAP, Google, AWS Cognito etc), Identity Providers (like Okta, Shibboleth, Ping, OneLogin, KeyCloak), Databases (like MySQL, Maria DB, PostgreSQL) and many more. You can configure your existing directory/user store or add users in miniOrange.

• Setup miniOrange as IDP
• Setup AD as User Directory
• Setup External IDP

• To add your users in miniOrange there are 2 ways:

1. Create User in miniOrange

2. Bulk Upload Users

1. Create User in miniOrange

• Click on Users >> User List >> Add User.



• Here, fill the user details without the password and then click on the Create User button.



• After successful user creation a notification message "An end user is added successfully" will be displayed at the top of the dashboard.



• Click on On Boarding Status tab. Check the email, with the registered e-mail id and select action Send Activation Mail with Password Reset Link from Select Action dropdown list and then click on Apply button.



• Now, Open your email id. Open the mail you get from miniOrange and then click on the link to set your account password.
• On the next screen, enter the password and confirm password and then click on the Single Sign-On (SSO) reset password button.



• Now, you can log in into miniOrange account by entering your credentials.

2. Bulk Upload Users in miniOrange via Uploading CSV File.

• Navigate to Users >> User List. Click on Add User button.



• In Bulk User Registration Download sample csv format from our console and edit this csv file according to the instructions.



• To bulk upload users, choose the file make sure it is in comma separated .csv file format then click on Upload.



• After uploading the csv file successfully, you will see a success message with a link.
• Click on that link you will see list of users to send activation mail. Select users to send activation mail and click on Send Activation Mail. An activation mail will be sent to the selected users.

• Click on External Directories >> Add Directory in the left menu of the dashboard.



• Select Directory type as AD/LDAP.



1. STORE LDAP CONFIGURATION IN MINIORANGE: Choose this option if you want to keep your configuration in miniOrange. If active directory is behind a firewall, you will need to open the firewall to allow incoming requests to your AD.
2. STORE LDAP CONFIGURATION ON PREMISE: Choose this option if you want to keep your configuration in your premise and only allow access to AD inside premises. You will have to download and install miniOrange gateway in your premise.




• Enter LDAP Display Name and LDAP Identifier name.
• Select Directory Type as Active Directory.
• Enter the LDAP Server URL or IP Address against LDAP Server URL field.
• Click on Test Connection button to verify if you have made a successful connection with your LDAP server.



• In Active Directory, go to the properties of user containers/OU's and search for Distinguished Name attribute.



• Enter the valid Bind account Password.
• Click on Test Bind Account Credentials button to verify your LDAP Bind credentials for LDAP connection.



• Search Base is the location in the directory where the search for a user begins. You will get this from the same place you got your Distinguished name.



• Select a suitable Search filter from the drop down menu. To use custom Search Filter select "Write your Custom Filter" option and customize it accordingly.



• You can also configure following options while setting up AD. Enable Activate LDAP in order to authenticate users from AD/LDAP. Click on the Save button to add user store.




Here's the list of the attributes and what it does when we enable it. You can enable/disable accordingly.

Attribute	Description
Activate LDAP	All user authentications will be done with LDAP credentials if you Activate it
Sync users in miniOrange	Users will be created in miniOrange after authentication with LDAP
Fallback Authentication	If LDAP credentials fail then user will be authenticated through miniOrange
Allow users to change password	This allows your users to change their password. It updates the new credentials in your LDAP server
Enable administrator login	On enabling this, your miniOrange Administrator login authenticates using your LDAP server
Show IdP to users	If you enable this option, this IdP will be visible to users
Send Configured Attributes	If you enable this option, then only the attributes configured below will be sent in attributes at the time of login



• Click on Save. After this, it will show you the list of User stores. Click on Test Connection to check whether you have enter valid details. For that, it will ask for username and password.



• On Successful connection with LDAP Server, a success message is shown.
• Click on Test Attribute Mapping.



• Enter a valid Username. Then, click on Test. Mapped Attributes corresponding to the user are fetched.



• After successful Attribute Mapping Configuration, go back to the ldap configuration and enable Activate LDAP in order to authenticate users from AD/LDAP.

Refer our guide to setup LDAPS on windows server.

User Import and Provisioning from AD

• Go to Settings >> Product Settings in the Customer Admin Account.



• Enable the "Enable User Auto Registration" option and click Save.



• (Optional) To send a welcome email to all the end users that will be imported, enable the "Enable sending Welcome Emails after user registration" option and click Save.



• From the Left-Side menu of the dashboard select Provisioning.



• In Setup Provisioning tab select Active Directory in the Select Application Drop Down.
• Toggle the Import Users tab, click on Save button.



• On the same section, switch to Import Users section.
• Select Active Directory from the dropdown and click on the Import Users tab, to import all the users from Active Directory to miniOrange.



• You can view all the Users you have imports by selecting Users >> User List from Left Panel.



• All the imported users will be auto registered.
• These groups will be helpful in adding multiple 2FA policies on the applications.

miniOrange integrates with various external user sources such as directories, identity providers, and etc.

• Okta
• ADFS
• Ping
• AWS Cognito
• Many more

Not able to find your IdP or Need help setting it up?

Contact us or email us at idpsupport@xecurify.com and we'll help you setting it up in no time.

5. Adaptive Authentication with Salesforce Community

A. Restricting access to Salesforce Community with IP Blocking

You can use adaptive authentication with Salesforce Community Single Sign-On (SSO) to improve the security and functionality of Single Sign-On. You can allow a IP Address in certain range for SSO or you can deny it based your requirements and you can also challenge the user to verify his authenticity. Adaptive authentication manages the user authentication bases on different factors such as Device ID, Location, Time of Access, IP Address and many more.

You can configure Adaptive Authentication with IP Blocking in following way:

• Login to Self Service Console >> Adaptive Authentication.
• Add a Policy Name for your Adaptive Authentication Policy.



• Select your Action for behaviour Change and Challenge Type for user from the Action for behaviour Change Section.





Action for behaviour Change Options :




Attribute	Description
Allow	Allow user to authenticate and use services if Adaptive authentication condition is true.
Challenge	Challenge users with one of the three methods mentioned below for verifying user authenticity.
Deny	Deny user authentications and access to services if Adaptive authentication condition is true.




Challenge Type Options :




Attribute	Description
User second Factor	The User needs to authenticate using the second factor he has opted or assigned for such as OTP over SMS PUSH Notification OTP over Email And 12 more methods.
KBA (Knowledge-based authentication)	The System will ask user for 2 of 3 questions he has configured in his Self Service Console. Only after right answer to both questions user is allowed to proceed further.
OTP over Alternate Email	User will receive a OTP on the alternate email he has configured threw Self Service Console. Once user provides the correct OTP he is allowed to proceed further.



• Now Enable Enable IP Restriction option from the IP RESTRICTION CONFIGURATION section to configure custom IP range.



• Select the Action you want to perform if the IP address is out of the range. i.e. Allow, Challenge & Deny.
• Specify the IP Address range for which you want above setting to reflect. You can add more than one IP Address ranges by clicking on following button +.
• Scroll to the end and click on save.

B. Adaptive Authentication with Limiting number of devices.

Using Adaptive Authentication you can also restrict the number of devices the end user can access the Services on. You can allow end users to access services on a fixed no. of devices. The end users will be able to access services provided by us on this fixed no. of devices.

You can configure Adaptive Authentication with Device Restriction in following way


• Login to Self Service Console >> Adaptive Authentication.
• Add a Policy Name for your Adaptive Authentication Policy.
• Select your Action for behaviour Change and Challenge Type for user from the Action for behaviour Change Section.




• Scroll down to Device Configuration section and enable Allow User to Register Device option to allow users to register their devices.
• Enter the Number of Devices which are allowed to register in field next to Number of Device Registrations Allowed
• Choose Action if number of devices exceeded (This will override your setting for Action for Behaviour Change.)
1. Challenge: The user needs to verify himself using any of the three methods mentioned in table in step 5.1
2. Deny : Deny users access to the system
• Enable option Send email alerts to Users if number of Device registrations exceeded allowed count if you want to alert the user about no of devices exceeding the limit. Save the configuration.

C. Add Adaptive Authentication policy to Salesforce Community.

• Login to Self Service Console >> Policies.
• Click on Edit option for predefined app policy.



• Set your application name in the Application and select password as Login Method.
• Enable Adaptive Authentication on Policy page and select the required restriction method as an option.
• From Select Login Policy dropdown select the policy we created in last step and click on save.

D.Notification and Alert Message.

This section handles the notifications and alerts related to Adaptive Authentication.It provides the following options :

• Get email alerts if users login from unknown devices or locations : Admin need to enable this option to enable receiving alerts for different alert options.
  
  
  

Option	Description
Challenge Completed and Device Registered	Enabling this option allows you to send an email alert when an end-user completes a challenge and registers a device.
Challenge Completed but Device Not Registered	Enabling this option allows you to send an email alert when an end-user completes a challenge but do not registers the device.
Challenge Failed	Enabling this option allows you to send an email alert when an end-user fails to complete the challenge.






• Next subsection is Send email alerts which allows us to enable or disable alerts for admin and end-users. To enable alerts for admins, you can enable the “Administrators” switch button.




• In case you want multiple admins accounts to receive alerts then you can enable the option for admin and then enter the admin emails separated by a ‘,’ in the input field next to Administrators email to receive alerts label. To enable alerts for the end-users, you can enable the “End Users” switch button.
• In case you want to customize the deny message that end user receive in case his authentication denied due to adaptive policy, you can do this by entering the message inside “Deny message for Adaptive Authentication” textbox.


How to add a trusted Device

1. When End-user log in to the self service console after the policy for device restriction is on, he is provided the option to add the current device as a trusted device.

External References

• Guide For Salesforce Single Sign On (SSO)
• Guide For Single Sign On (SSO)
• Learn more on miniOrange Identity Provider (IdP)
• What is 2FA/MFA? Enable 2FA/MFA on top of SSO for Salesforce
• Learn more about user and group provisioning