# Forge External Oauth2 doesn't support Atlassian Oauth?

**URL:** <https://community.developer.atlassian.com/t/forge-external-oauth2-doesnt-support-atlassian-oauth/55283>\
**Category:** Forge Platform and Tools\
**Tags:** forge-external-auth, macro\
**Created:** [January 22, 2022, 7:59pm UTC](https://community.developer.atlassian.com/t/forge-external-oauth2-doesnt-support-atlassian-oauth/55283 "2022-01-22T19:59:59Z")\
**Posts on this page:** 1\
**Showing post:** 8

<div class="post-metadata">

**Author:** ![zsims](https://sea1.discourse-cdn.com/atlassiandeveloper/user_avatar/community.developer.atlassian.com/zsims/32/41907_2.png) [@zsims](https://community.developer.atlassian.com/u/zsims)\
**Post date:** [February 9, 2022, 11:51pm UTC](https://community.developer.atlassian.com/t/forge-external-oauth2-doesnt-support-atlassian-oauth/55283/8 "2022-02-09T23:51:09Z")

</div>

You’re not missing anything. To shed some light on why it’s currently disabled: OAuth apps today don’t go through an installation consent flow by admins as they’re not “installed into” sites.  
With Forge user consent and external authentication, there’s not a clear distinction between the app asking for Forge scopes and the regular OAuth consent flow which ends up very confusing for users/admins. It’s very likely the Atlassian OAuth restriction will be removed from external authentication when we’re rolled out finer grain admin controls for OAuth apps or removed Forge user consent per [We're removing the allow access prompt for Forge apps](https://community.developer.atlassian.com/t/were-removing-the-allow-access-prompt-for-forge-apps/53035)

---

_[View the full topic](https://community.developer.atlassian.com/t/forge-external-oauth2-doesnt-support-atlassian-oauth/55283)._