OAuth2 authorization for Private Apps issues

Developer Support APIs & Integrations
1

Hello,

Our customers use Private Apps to integrate with our product (3CX Phone System). Basically they create a Private App, configure the required scopes, and then configure the Client ID and Client Secret on our side to start the OAuth2 authorization flow. When they do this, they get this error from HubSpot:

Couldn’t complete the connection

The app developer doesn’t have permissions to request the set of scopes. Please contact the app developer.

edossantos_0-1648639669371.png

We verified that the scopes required by us, are exactly the same as the ones declared in the Private App:

  • crm.objects.contacts.read
  • crm.objects.contacts.write
  • crm.objects.companies.read
  • crm.objects.owners.read
  • timeline

edossantos_1-1648639779141.png
edossantos_1-1648639779141.png752×211 7.05 KB

In addition, we created a public app using a developer account, and configured the same scopes, and from there the OAuth2 authorization works fine.

Please note that we’re not using the Access Token that you can directly get from the Private App page, instead we use the Client ID and Client Secret which are visible under “Show other credentials” for the private app. Is there any known issue related to OAuth2 authorizations with private apps? Any hint you can provide?

Thank you.

2

I’m wondering if auth2 authorizations worked at any point for private apps.

https://community.hubspot.com/t5/APIs-Integrations/The-app-developer-doesn-t-have-permissions-to-request-the-set-of/m-p/605360#M52063

3

Yes, this was definitely working in the past, we tested this in many installations, and we have many customers that were using this without any issues. This was broken just now…

4

@edossantos @dennisedson Good to know, I picked a **bleep** day to try auth with Private Apps.

Others seem to have similar problem since yesterday (https://community.hubspot.com/t5/APIs-Integrations/Private-App-OAuth/m-p/603764#M51966).

5

Hey all,

The issue here appears to be that you are trying to install a private app as a public OAuth app. As @edossantos mentioned it was working, but it was undocumented and not the intent of private apps. Earlier this week, the product team closed that loop.

If you have a public app, the best route to authenticate is with OAuth. If you are building an app for a single portal, the better option would be to use a private app as documented here.

Another reason that you would use OAuth is if you needed access to our webhooks which are not available yet for private apps.

Sorry for any confusion this may have created!