Salesforce Update: Enable Multi-Factor Authentication
Salesforce prepares an update concerning the security of the Salesforce products. Since February 1, 2022, Salesforce will begin requiring customers to enable multifactor authorization (MFA) to access Salesforce products.
For more information, go to:
Important Notes
| If you cannot meet the MFA requirement until February 1, 2022, you would not be aligned with the terms of the Salesforce usage agreement. If you have any questions regarding the MFA rollout, we recommend creating a case to Salesforce. |
-
Although the MFA requirement is contractual, and users should have the configured MFA when logging in through the user interface, starting February 1, 2022, users will not be blocked from logging into Salesforce unless MFA is configured.
-
Salesforce will announce any features added in Salesforce Core for enforcement, and the enforcement will occur over several releases. We recommend reading Multi-Factor Authentication (MFA) Enforcement Roadmap.
-
If you are planning a staged MFA rollout for different categories of users, Salesforce highly recommends starting with administrators because they control data and security within your Salesforce org.
Prepare your CT Mobile to Salesforce Update
Since CT Mobile 2.1, all standard CT Mobile releases include the OAuth 2.0 protocol to meet MFA.
-
If you are using the standard CT Mobile app from the App Store, no additional action is required on your part.
-
If you are using the custom CT Mobile 2.1 or higher with the enabled OAuth 2.0, no additional action is required on your part.
We notify you to perform the following actions:
-
If you are using the custom CT Mobile 2.1 or higher and have disabled OAuth 2.0 by custom code, enable OAuth 2.0 to provide MFA.
-
If you are using the standard CT Mobile 1.9.6 or custom CT Mobile below 2.1, do one of the following actions:
-
Migrate to the latest version of the standard CT Mobile app.
-
Enable OAuth 2.0 in your CT Mobile app by custom code.
-