Hi there, we are having an issue with a user where when they try to do the server to server oauth in salesforce with their subdomian, they see the following screen, but oddly it works for us just using

login

as the subdomian during auth. Do they need to set some permissions as their salesforce admin to allow oauth apps? Or do we have to make them create their own oauth app doing something like this https://composio.dev/auth/salesforce? Thanks. https://cdn.discordapp.com/attachments/1511716076407357450/1511716076747100333/Screenshot_2026-06-02_at_2.30.34_PM.png?ex=6a2176cf&is=6a20254f&hm=a26470a99a11e170f77e904ac73079e66d70653485f04776bdd0a141e9efb5a1&

Hi there, Thanks for the detail, and the fact that it works with

login

but not the user's own subdomain is a useful clue. The most common cause here is org-side: when you auth against a specific My Domain (

company.my.salesforce.com

) you hit that org directly, and many Salesforce orgs restrict which connected apps users can authorize. In that case the user's Salesforce admin needs to approve or install the connected app for that org (under their Connected Apps / OAuth app access settings). The

login

route works because it goes through Salesforce's shared login service rather than the org's own policy. Creating your own OAuth app is an option if you want full control, but it usually isn't required just to clear an admin-approval block. Before you go down either path, could you share the exact error text shown on that screen for the failing user? The wording (for example whether it mentions the app needing to be installed or approved) will tell us definitively whether it's the org policy above or something else, so you don't chase the wrong fix. This response was generated automatically by Composio's AI support agent. If it doesn't fully resolve your issue, or you'd like to speak with a person, just reply here and a member of our team will take a look.