<iframe src="https://www.googletagmanager.com/ns.html?id=GTM-M74D8PB" height="0" width="0" style="display:none;visibility:hidden">
Loading
Skip to NavigationSkip to Main Content
0D54z0000AA0FHtCQNOkta Classic EngineSingle Sign-OnAnswered2025-07-06T09:00:35.000Z2024-06-03T07:40:57.000Z2024-06-28T16:26:03.000Z

l770k (l770k) asked a question.

Using Okta to Authenticate users into an Azure WebApp / Enterprise Application SSO.

We have an ASP.NET web-based Enterprise Application deployed in Microsoft Azure. Currently the application uses SQL stored user accounts and Simple Membership to handle the user authentication.

 

We are trying to migrate the application to use SSO with Okta as an IdP, and have followed the documentation here: https://help.okta.com/en-us/content/topics/provisioning/azure/azure-create-enterprise-app.htm and what we are experiencing is:

 

  1. When the user navigates to the web app, the authentication process initiates, which forwards the browser to the Okta login, and logs the user in.
  2. Once logged into Okta, the app is displayed in the Applications section, and when the app icon is clicked or the application is launched, the user is forwarded back to a Microsoft error page stating "Invalid Empty Request".

 

I've spent the past 3 days working with Microsoft's support technicians who have been trying to figure out why that's happening, and their end result was that they believe the error is coming from the Okta side, because everything they see on their end says authentication is successful. I've been able to verify this by using the built in SSO testing tool in the Enterprise Application.

 

Thank you in advance for any and all suggestions.


This question is closed.
Loading
Using Okta to Authenticate users into an Azure WebApp / Enterprise Application SSO.