1
down vote
favorite
I am working on a client solution that requires new features and functionality to be added to a cloud web application with OKTA Authentication. I’ve been able to create the new models, views, and controllers as per requirement, with no errors when I build the solution. When I run the application to test locally, the views load in the browser but no data and functionality, and a redirect on the URL, either running in the preconfigured DEV, STG, or PRD Azure environments.
< hhttp://localhost:1080/AuthServices/SignIn?ReturnUrl=%2f >
It’s not finding the authentication form, it has no user information, and the site is not loading properly. I’ve tried different thing, including removing the authentication all together, and setting authentication to non / in the web.config. The only thing I’ve not done yet is testing on the publishing side. Everything with OKTA is setup correctly as it’s working fine with the last deployed version of the solution, . Non non of those configurations were changed.
How can work around or disable this entirely so that I can test the application locally?
Thanks in advance!