# You are not allowed to access this app. okta-angular-oie-sample-quickstart

**URL:** <https://devforum.okta.com/t/you-are-not-allowed-to-access-this-app-okta-angular-oie-sample-quickstart/24399>\
**Category:** OAuth/OIDC\
**Tags:** api, widget, angularjs, angular\
**Created:** [May 30, 2023, 1:52pm UTC](https://devforum.okta.com/t/you-are-not-allowed-to-access-this-app-okta-angular-oie-sample-quickstart/24399 "2023-05-30T13:52:42Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![martin.b](https://avatars.discourse-cdn.com/v4/letter/m/9dc877/32.png) [@martin.b](https://devforum.okta.com/u/martin.b)\
**Post date:** [May 30, 2023, 2:38pm UTC](https://devforum.okta.com/t/you-are-not-allowed-to-access-this-app-okta-angular-oie-sample-quickstart/24399/2 "2023-05-30T14:38:05Z")

</div>

SOLVED:  
If anyone else comes across this error for these Interaction Code flows, there are three places to enable it.

1. On the org itself (otherwise you can’t set the next two)
2. On the authentication server (this was missing for me)
3. On the application

It is a shame the system logs did not indicate the failure in some way.

---

_[View the full topic](https://devforum.okta.com/t/you-are-not-allowed-to-access-this-app-okta-angular-oie-sample-quickstart/24399)._