<h3>Overview</h3>Salesforce will soon deprecate the Username-Password OAuth flow for Connected Apps and has issued compliance requirements for all integrations using this method.ScreenMeet v1.27 introduces a new OAuth-based authentication model that removes the dependency on a stored password and security token. This article guides existing ScreenMeet Salesforce customers through the steps required to migrate to the new authentication model after upgrading to v1.27 or later.Salesforce Compliance RequirementSalesforce has flagged the Username-Password OAuth flow as non-compliant and has notified affected orgs by email. Failure to complete this migration may result in authentication failures for the ScreenMeet integration. See <a target="_new" rel="noopener" href="https://help.salesforce.com/s/articleView?id=005232552&amp;type=1">Salesforce Help: 005232552</a> and <a target="_new" rel="noopener" href="https://help.salesforce.com/s/articleView?id=005225370&amp;type=1">Salesforce Help: 005225370</a> for details.<hr><h3>Prerequisites</h3><ul><li>Salesforce System Administrator access.</li><li>Access to the ScreenMeet Console at <a target="_new" rel="noopener" href="https://console.screenmeet.com">console.screenmeet.com</a>.</li><li>Existing ScreenMeet Salesforce integration previously configured (Service Account user already created and configured).</li></ul><hr><h3>Step 1: Install the v1.27 Package Upgrade</h3>Install the latest ScreenMeet package from AppExchange before proceeding with any configuration changes.<ol><li>Navigate to the ScreenMeet listing on AppExchange and click Get It Now.</li><li>Select your target org and follow the installation prompts.</li><li>Once installation completes, confirm the installed package version is v1.27 or later under Setup &gt; Installed Packages.</li></ol>Upgrade Does Not Break Existing FunctionalityInstalling v1.27 does not immediately change how the integration authenticates. Your existing username-password configuration will continue to work until you complete the migration steps in this guide. Proceed through the steps at a time that suits your change management process.<hr><h3>Step 2: Grant Connected App Access to the Service Account</h3>The ScreenMeet Service Account user must have the ScreenMeet Connected App explicitly enabled on the custom system permissions permission set you created during initial setup.Which Permission Set to UseThis step targets the custom permission set your Salesforce administrator created manually during initial setup, typically named <code>ScreenMeet Service System Permissions</code>.It contains system permissions such as Apex REST Services and API Enabled.This is not the managed <code>ScreenMeet Service</code> permission set installed with the package.If your org used a different name, locate it by checking the permission sets assigned to your ScreenMeet Service Account user. For reference, see <a target="_new" rel="noopener" href="https://docs.screenmeet.com/docs/salesforce-service-account-setup">Service Account Setup</a>.<ol><li>In Salesforce Setup, navigate to Permission Sets.</li><li>Open your custom ScreenMeet Service Account permission set (for example, <code>ScreenMeet Service System Permissions</code>).</li><li>Click Assigned Connected Apps.</li><li>Click Edit.</li><li>Move ScreenMeet from Installed Connected Apps to Enabled Connected Apps.</li><li>Click Save.</li></ol><hr><h3>Step 3: Grant Connected App Access to Agents, Supervisors, and Administrators</h3>All ScreenMeet users who log in to the console or use ScreenMeet features within Salesforce must also have access to the Connected App. The recommended approach is to create a dedicated permission set for this purpose.<ol><li>In Salesforce Setup, navigate to Permission Sets and click New.</li><li>Enter <code>ScreenMeet Console Access</code> as the label and click Save.</li><li>From the permission set overview, click Assigned Connected Apps.</li><li>Click Edit, move ScreenMeet to Enabled Connected Apps, and click Save.</li><li>Assign this permission set to all ScreenMeet agents, supervisors, and administrators.<ol><li>This permission set can be included in a permission set group as well</li><li>Example: ScreenMeet Agent permission set + ScreenMeet Console Access permission set = ScreenMeet Agent Permission Set group.</li></ol></li></ol><hr><h3>Step 4: Update the ScreenMeet Connected App Policy</h3>With Connected App access assigned to all users and the Service Account, update the Connected App policy to enforce the new authorization model.This Step Activates the New Authentication ModelSaving this change is the point at which the username-password flow is disabled for the ScreenMeet Connected App. Confirm Steps 2 and 3 are complete for all users before proceeding.<ol><li>In Salesforce Setup, use Quick Find to search for Manage Connected Apps.</li><li>Click ScreenMeet from the list.</li><li>Click Edit Policies.</li><li>Under Permitted Users, select Admin approved users are pre-authorized.</li><li>Click Save.</li></ol><hr><h3>Step 5: Remove Password and Security Token from ScreenMeet Console</h3>Version 1.27 no longer uses the Service Account password or security token for authentication. Clear these from the console configuration to complete the migration.<ol><li>Open <a target="_new" rel="noopener" href="https://console.screenmeet.com">console.screenmeet.com</a> and sign in.</li><li>Navigate to Organization &gt; Settings and Policies &gt; Salesforce Integration.</li><li>Make note of existing settings that are configured for the instance, as they will need to reconfigured in Step #4.<ol><li>It is suggested to take a screenshot(s) of the existing settings, such as where files are stored, agent obfuscation, etc.</li></ol></li><li>Press the “Reset to Default” button near the bottom of the page.<ol><li>This step is to clear the encrypted password/security token fields as they are no longer used.</li></ol></li><li>Reconfigure the Salesforce integration settings based on the noted desired settings from Step #3, including the Service Account username.</li><li>Click Save.</li><li>Click Configure and Validate Salesforce Org to confirm the integration is functioning.</li></ol>Password Never Expires PermissionThe <code>Password Never Expires</code> system permission on the Service Account is no longer required in v1.27 and later. You do not need to remove it, but it is no longer a dependency for the integration to function.<hr><h3>Verification</h3>After completing all steps, confirm the migration was successful:<ul><li>The Configure and Validate Salesforce Org button in the console returns a success status.</li><li>An agent with the <code>ScreenMeet Console Access</code> permission set can log in to <a target="_new" rel="noopener" href="https://console.screenmeet.com">console.screenmeet.com</a> via the Salesforce OAuth flow without errors.</li><li>Check the Salesforce Login History for the ScreenMeet Service Account user to confirm successful OAuth logins with no authentication failures.</li></ul>If Configure and Validate Salesforce Org fails, verify the following:<ul><li>The Service Account user has both the managed <code>ScreenMeet Service</code> permission set and your custom service system permissions permission set assigned.</li><li>The Connected App is listed under Enabled Connected Apps on your custom service system permissions permission set.</li><li>Login History shows OAuth attempts for the Service Account. If no attempts appear, the username entered in the console may be incorrect.</li></ul><hr><h3>Related Articles</h3><ul><li><a target="_new" rel="noopener" href="https://docs.screenmeet.com/docs/salesforce-service-account-setup">Service Account Setup</a></li><li><a target="_new" rel="noopener" href="#">ScreenMeet Permissions and Roles Overview</a></li><li><a target="_new" rel="noopener" href="https://help.salesforce.com/s/articleView?id=005232552&amp;type=1">Salesforce Help: Username-Password Flow Deprecation</a></li><li><a target="_new" rel="noopener" href="https://help.salesforce.com/s/articleView?id=005225370&amp;type=1">Salesforce Help: Connected App Security Requirements</a></li></ul>

Upgrading to ScreenMeet for Salesforce v1.27: Migrating Away from Username-Password Authentication

ScreenMeet 2025 Release Notes

403 Forbidden while making API request

404 NO_ACCESS

Installing ScreenMeet for Salesforce

Advanced CSS customization

AI Assist

AI Assist Overview

Overview

AI Release Notes Q4 24

Requirements

AI Summarization

AI Summary History

AI Summary Privacy

AI Summary Studio

Android SDK Quickstart

How-to: Setup the app for Laser Pointer

How-to: Display a video stream to the end-user

Egress IP Addresses

AWS S3 File Storage

Configuring ScreenMeet / Microsoft Entra ID integration

Signing into ScreenMeet console with Microsoft Entra ID (Azure AD)

Beam Client: Installation, Deployment, and Configuration Guide

Beam Groups: Setup, Settings, and Access Management

Beam Release Notes Q1 22

Beam Release Notes Q1 23

Beam Release Notes Q1 24

Beam Release Notes Q2 22

Beam Release Notes Q2 23

Beam Release Notes Q2 24

Beam Release Notes Q3 23

Beam Release Notes Q3 22

Beam Release Notes Q4 22

Beam Release Notes Q4 24

New Remote Support Client for Mac

Canvas

Certificate-Based Device Validation

Clone - Remote Support Release Notes Q4 23

Clone - Test ScreenMeet 2025 Release Notes

File Storage on AWS

Configuring Information Security & PII

Creating a Custom UI

Custom Copy

Cobrowse Demo

CoBrowse Deployments

Events

Hotkeys

Localization

CoBrowse Release Notes Q1 23

CoBrowse Release Notes Q1 22

CoBrowse Release Notes Q1 24

CoBrowse Release Notes Q2 22

CoBrowse Release Notes Q2 23

CoBrowse Release Notes Q2 24

CoBrowse Release Notes Q3 22

CoBrowse Release Notes Q3 23

CoBrowse Release Notes Q3 24

CoBrowse Release Notes Q4 22

CoBrowse Release Notes Q4 23

CoBrowse Release Notes Q4 24

Remote Control

Remove End Cobrowse Button

Cobrowse Script

Cobrowse Settings

Starting a Session with a URL

Configuration and validation troubleshooting

Configure API service

Configure ScreenMeet for a New Salesforce Sandbox

Configure ScreenMeet to only show on specified tables

Configuring Environment Variables

Configuring Webhooks for Data Sync

Connecting to ChromeOS devices

Connecting to Mac devices

Connection Information

Create Multiple Sessions

Creating a Replay Recording

Creating a session

Custom Consent Message

Custom permission configuration for ServiceNow

Custom URL

Custom Windows Tools

Deploying a Pre-installed Client

Developer Notes

Developer Notes (3.0.11)

Device Requirements

Enable ScreenMeet for Omnichannel Chat Widget

Enabling features within the Salesforce + ScreenMeet component