top of page
Search

Salesforce Identity Connect Retirement: What You Need to Know and Alternative Solution Options

  • Writer: Atomstrix Technologies
    Atomstrix Technologies
  • Jun 28, 2024
  • 3 min read

Updated: Apr 1


 

A Technological Advancement


Salesforce has decided to end its Identity Connect product. This change has led many users to look for alternatives. AtomicExstric is a trusted partner in finance. It serves hundreds of Salesforce customers. We're here to help you through this transition. Let's discuss what you need to know and how to move forward.





 

Impact of the Retirement

Salesforce Identity Connect will be retired. This will happen when your current contract ends (Order End Date). This means all users must switch to a new solution before that date. They must do this to keep access to their Salesforce instance. No new features will be added. But, existing users can use the product until its retirement date.


Why is Salesforce Retiring Identity Connect?

When Identity Connect launched, most Salesforce customers used on-premises Active Directory. They were new to the cloud. Now, many have fully shifted to the cloud. This shift makes Identity Connect, a special tool for this purpose, less necessary. High-quality user provisioning solutions from other providers are also common. This makes Identity Connect redundant.


Alternatives to Identity Connect

Switching identity solutions might feel daunting, but there are several robust alternatives available:


  1. Salesforce Identity Salesforce Identity is a tool that manages user identities, logins, and access to Salesforce resources. It also provides continued support, ensuring a smooth transition.

  2. Third-party identity management solutions. Several third-party solutions can integrate with Salesforce, offering functionalities similar to it's:

  • Okta: Offers SSO, user setup, mobile device management, two-factor authentication, multi-factor authentication, API linking, and more.

  • Auth0 is a platform. It has SSO and MFA. It also has user management. It can link to third-party and custom databases.

  • Microsoft Azure Active Directory (Azure AD) makes identity management simpler. It has SSO for many apps and services. It supports custom domains and social media logins.

  • G Suite has features for security. They include 2FA, SSO, and OpenID Connect. It also has security tips from industry best practices.

  1. Custom Development Developing custom solutions sync identity data between Salesforce and other systems. It provides more control and flexibility. This approach requires resources. But, it lets you tailor identity processes to specific needs.


Detailed Solution Comparison

To help you decide, here’s a comparison of key features of these solutions:


  • Okta:

  • SSO: Yes

  • User Provisioning: Yes

  • 2FA: Yes

  • Adaptive MFA: Yes

  • Mobile Device Management: Yes

  • API Integration: Extensive

  • Auth0:

  • SSO: Yes

  • User Provisioning: Yes

  • 2FA: Yes

  • MFA: Yes

  • API Integration: Robust

  • Custom Database Integration: Yes

  • Azure AD:

  • SSO: Yes

  • User Provisioning: Yes

  • 2FA: Yes

  • MFA: Yes

  • Custom Domain Support: Yes

  • Social Media Account Registration: Yes

  • G Suite:

  • SSO: Yes

  • 2FA: Yes

  • OpenID Connect Integration: Yes

  • Account Security Recommendations: Yes

  • Cross-App Integration: Extensive


Steps to Transition

  1. Review the current use. Find which of your Salesforce orgs use Identity Connect. Also, find the servers where it’s installed. Determine if it’s used for user provisioning, SSO, or both.

  2. Explore other options. Check if your organization already has a tool that can do what Identity Connect does. For instance, if you’re moving to Azure AD, consider using Microsoft’s Azure AD Connector for Salesforce. If not, explore other marketplace options like Okta, Auth0, and ForgeRock.

  3. Plan the migration once you’ve picked a new provisioning tool. It will involve moving users and replacing Identity Connect. Ensure you remove Identity Connect from any installed server and delete downloaded binaries. Also, remove the Identity Connect Managed Package from your orgs.

  4. Inform affected users about the transition plan and timeline. This is especially important for those with the Identity Connect user permission set.


Risks of Inaction

If you don't transition before your Identity Connect subscription ends:


  • New Users: Won’t be provisioned to Salesforce.

  • Existing Users: Will stop receiving updates from Active Directory.

  • Deactivated Users: Will still be active in Salesforce.

  • SSO Disruption: SSO between Active Directory and Salesforce will stop working.

These issues can lead to business interruptions and security concerns. So, start to evaluate your migration path. Plan your transition as soon as you can.


 

Final Thoughts

Salesforce Identity Connect is retiring. This is a chance to reassess and maybe improve your identity strategy. You have many robust options to ensure seamless access to Salesforce. They include Salesforce Identity, Okta, Auth0, Azure AD, and G Suite.


At AtomicExstric, we specialize in guiding our clients through transitions like these. Our team is ready to help you evaluate your options and implement the best solution for your needs. Don’t wait until the last minute—start planning your transition now to avoid any disruptions.


If you have questions or need help, please reach out. Our team is here to guide you. We will help you continue using Salesforce without interruption.


 

 
 
 

Comments

bottom of page