# OAuth2 authorization for Private Apps issues

**URL:** <https://community.hubspot.com/t/oauth2-authorization-for-private-apps-issues/54078>\
**Category:** APIs & Integrations\
**Created:** [March 30, 2022, 11:34am UTC](https://community.hubspot.com/t/oauth2-authorization-for-private-apps-issues/54078 "2022-03-30T11:34:11Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![edossantos](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/edossantos/32/92090_2.png) [@edossantos](https://community.hubspot.com/u/edossantos)\
**Post date:** [March 30, 2022, 11:34am UTC](https://community.hubspot.com/t/oauth2-authorization-for-private-apps-issues/54078/1 "2022-03-30T11:34:11Z")

</div>

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](https://d2qpr2jzcazej7.cloudfront.net/original/3X/c/a/ca317d77495ca135ced856c060a709e0b15efee3.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](https://d2qpr2jzcazej7.cloudfront.net/original/3X/d/0/d06342bfaf27cdf676bfd91366b81913750b55bc.png)

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.

---

<div class="post-metadata">

**Author:** ![SeanCullen](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/seancullen/32/52876_2.png) [@SeanCullen](https://community.hubspot.com/u/SeanCullen)\
**Post date:** [March 31, 2022, 4:44pm UTC](https://community.hubspot.com/t/oauth2-authorization-for-private-apps-issues/54078/2 "2022-03-31T16:44:36Z")

</div>

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](https://community.hubspot.com/t5/APIs-Integrations/The-app-developer-doesn-t-have-permissions-to-request-the-set-of/m-p/605360#M52063)

---

<div class="post-metadata">

**Author:** ![edossantos](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/edossantos/32/92090_2.png) [@edossantos](https://community.hubspot.com/u/edossantos)\
**Post date:** [March 31, 2022, 5:39pm UTC](https://community.hubspot.com/t/oauth2-authorization-for-private-apps-issues/54078/3 "2022-03-31T17:39:02Z")

</div>

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…

---

<div class="post-metadata">

**Author:** ![SeanCullen](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/seancullen/32/52876_2.png) [@SeanCullen](https://community.hubspot.com/u/SeanCullen)\
**Post date:** [March 31, 2022, 6:06pm UTC](https://community.hubspot.com/t/oauth2-authorization-for-private-apps-issues/54078/4 "2022-03-31T18:06:54Z")

</div>

@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](https://community.hubspot.com/t5/APIs-Integrations/Private-App-OAuth/m-p/603764#M51966)).

---

<div class="post-metadata">

**Author:** ![dennisedson](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/dennisedson/32/28044_2.png) [@dennisedson](https://community.hubspot.com/u/dennisedson)\
**Post date:** [March 31, 2022, 7:14pm UTC](https://community.hubspot.com/t/oauth2-authorization-for-private-apps-issues/54078/5 "2022-03-31T19:14:56Z")

</div>

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](https://developers.hubspot.com/docs/api/oauth-quickstart-guide). If you are building an app for a single portal, the better option would be to use a private app as [documented here](https://developers.hubspot.com/docs/api/private-apps).

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!
