Need Help? We are right here!
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"|
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.
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 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.
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.
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.
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.
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.
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 Shibboleth, Ping, Okta, OneLogin, KeyCloak), Databases (like MySQL, Maria DB, PostgreSQL) and many more.
|Application Name||Salesforce Community|
|SP Entity ID or Issuer||https://[yourdomain].my.salesforce.com/?so=[organization_id]|
|Single Logout URL||https://customdomain.my.salesforce.com|
Test SSO login to your Salesforce Community account with miniOrange IdP:
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.
1. Create User in miniOrange
2. Bulk Upload Users in miniOrange via Uploading CSV File.
Here's the list of the attributes and what it does when we enable it. You can enable/disable accordingly.
|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|
|Backup 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|
Refer our guide to setup LDAPS on windows server.
miniOrange integrates with various external user sources such as directories, identity providers, and etc.
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:
|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.|
|User second Factor||The User needs to authenticate using the second factor he has opted or assigned for such as
|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.|
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
C. Add Adaptive Authentication policy to Salesforce Community.
Our Other Identity & Access Management Products