
2doec (2doec) asked a question.
Hi guys!
I've created a simple single page app using React, and followed the walktrough listed here:
https://developer.okta.com/docs/guides/sign-into-spa-redirect/angular/main/
when I tried to test, and clicked the login button, nothing happened, checking the netwroking I saw this requests going toward okta from the web app:
https://[prod_domain_of_my_okcta].okta.com/oauth2/default/.well-known/openid-configuration
and got this response:
{"errorCode": "E0000015",
"errorSummary": "You do not have permission to access the feature you are requesting",
"errorLink": "E0000015",
"errorId": "oaeO_TeJhDhSvS6PpIewlhKGA",
"errorCauses": []
}
no other networking or other indication in the app
then I tried the same scenario but this time changed the to my dev okta about, and it worked properly(returned list of configurations , with the same url (different org domain)
not much documentation about this behaviour so Ill be happy to hear any advice
thanks!

Hi @2doec (2doec) , Thank you for reaching out to the Okta Community!
The error seems to suggest that what you are lacking is most probably a feature flag.
I recommend reaching out to your Okta Account Executive to confirm feature parity between the environments as some may require a different type of SKU. If you are already entitle to the features, the Support team can enable them for you.
If my answer helped, remember to mark it as best to increase its visibility for other members of the Okta Community who might have the same questions as you.
Hope my answer helps!
--------------------------------
Community members help others by clicking Like or Select as Best on responses. Try it today.
Hi Muhai Negotia!
Can you specify what could be the name of this missing feature toggle?
Wow, really butchered my name there :)) .
Anyway, don't know the specific feature flag. That is why I recommended checking org feature parity.
I've also came across this older post discussing a similar issue, so I recommend checking there as well, but please note that there's a reference there to "support@okta.com" - that email address is no longer valid. You can open a case here if needed.
https://devforum.okta.com/t/error-code-e0000015-after-following-net-4-x-tutorial/1135/3
Good luck!