After the release of Veeva CRM app version 262.3.205 users who rely on Delegated Authentication will be unable to authenticate on the iOS app unless they complete the instructions detailed here: <Veeva Connect Post> prior to the release date.
Identifying whether an organization or specific users rely on Delegated Authentication and completing the required updates is critical. Below are the two primary checks administrators should perform in Salesforce to generate the list of Delegated Authentication users who need to update their Salesforce User Access Policy to grant the Use Any API Auth system permission.
1. Check the Org-Level Setting
This determines if the Salesforce environment is configured to delegate authentication to an external endpoint:
- Log in to Salesforce Setup.
- In the Quick Find box, search for and select Single Sign-On Settings.
- Locate the Delegated Authentication section.
- Inspect the Delegated Gateway URL field (note: if Disable login with Salesforce credentials is unselected, then the Delegated Gateway URL is not being used and you are not using Delegated Authentication):
- Populated with a URL (e.g., [https://auth.customerdomain.com/](https://auth.customerdomain.com/)...): The org has Delegated Authentication enabled and actively routed.
- Blank / Empty: The org is not using Delegated Authentication (they either use standard passwords or SAML-based Single Sign-On).
2. Identify Specific Users and Profiles via SOQL and Org Configuration Setup
Even if the gateway URL is configured, Delegated Authentication only applies to users whose Profile or Permission Set has the specific system permission: Is Single Sign-On Enabled (API name: PermissionsIsSsoEnabled).
Important note for the Is Single Sign-On Enabled setting: Despite being named "Is Single Sign-On Enabled," in Salesforce this checkbox is part of the configuration that allows users to login with Delegated Authentication, and not SFDC credentials (CRM Guide). Some customers may use this to remove the option to login with SFDC credentials, even if they are set up with a different Single Sign-on login method, like SAML/OAuth2 Authentication. It is important to confirm if Delegated Gateway URL is populated, as well as, if users are logging in with “Other Apex API” in the Org Login History (Settings > Login History). “SOAP API” will be populated in the Login Subtype column.
Run the following queries in Developer Console, Workbench, or your API tool:
- Find active users whose Profile enforces Delegated Auth:
SELECT Id, Username, Name, Profile.Name, IsActive
FROM User
WHERE IsActive = TRUE
AND Profile.PermissionsIsSsoEnabled = TRUE- Find active users assigned Delegated Auth via Permission Sets:
SELECT AssigneeId, Assignee.Username, Assignee.Name, PermissionSet.Name
FROM PermissionSetAssignment
WHERE PermissionSet.PermissionsIsSsoEnabled = TRUE
AND Assignee.IsActive = TRUE-
Check Single Sign-On Settings in Settings to confirm that Delegated Authentication Gateway is populated
If these queries above return zero rows, no active users are routing through the Delegated Gateway. If the queries return users, then check these users to confirm the “Other Apex API” in the Login History (Settings > Login History). “SOAP API” will be populated in the Login Subtype column.
Related Documentation:
CRM Help Documentation: N/A