Dodi's Tips For Upcoming Salesforce Access Security Changes (July 1)
Dodi Friedenberg, the legend, has given me permission to share her original post here and we all need to absorb and understand this! Show her love on LinkedIn, she is awesome.
Her post follows bellow:
Important updates for Salesforce Admins:
1) On a rolling basis starting July 1, users with System Administrator privileges will no longer be able to use the Salesforce Authenticator App to log in and will be required to set up phishing-resistant multi-factor authentication, such as Windows Hello or Touch ID on Mac, if you have those enabled, or physical key (e.g. YubiKey or Google Titan). A Password Manager like Bitwarden may also be adequate.
Here are steps you can start taking today:
a. Make a note of your Org’s ID and keep it somewhere safe. Find it in Setup->Company Information (in case you need to log a case with Salesforce later)
b. Setup->Identity Verification, select “Let users verify their identity with a built-in authenticator such as Touch ID or Windows Hello” and save.
c. Each user with the System Administrator profile - or with Modify All Data, View All Data, Customize Application, or Author Apex - must specify a “Built-in” authenticator.
Click the Avatar or photo top right in Salesforce, choose “Settings,” choose “Advanced User Details,” scroll down to “Built-in Authenticators.” Click “Add.” Authenticate as you normally do. Click “Register.” Since I didn’t have Windows Hello enabled, but do use Bitwarden, this popped up Bitwarden for me. Under “Save passkey,” I chose my org. Next I named the Built-in Authenticator and Saved. (The default name says #1. You may have more than one in your password vault, but it may or may not be possible to add more than one Built-in Authenticator per Salesforce org.)
Link 1
Link 2
2) “Step-Up Authentication” - a requirement to reauthenticate when exporting - and perhaps also for viewing - reports. On or after May 27, we can tweak how often users will need to reauthenticate in order to export (or view?) reports - between 2 and 120 minutes. Default is 120 minutes. Setup->Identity Verification->“Require step-up authentication within cool-down period” session-level policy for Reports and Dashboards.
Link 3
Link 4
3) Email-based login will become the default login experience for the UI of login.salesforce.com and test.salesforce.com - scheduled to start in September. While users can still choose to log in with a username and password, prepare them for email to appear as the primary option.
Link 5
4) Salesforce now sends email only from verified domains. If you haven’t already set up (or updated) DKIM, here are two resources:
Video
Article
~ END OF HER POST ~
My thoughts: these changes are total overcorrections by Salesforce. Instead of feeling like security, they come across as an in-your-face attempt to detach us from the UI of the system. Anyone else feel the same?