Press Ctrl / CMD + C to copy this to your clipboard.
This post will be reported to the moderators as potential spam to be looked at
We've encountered very strange issue after deploying Umbraco to Azure App Service and enabling pre-authentication for it. Single Sign-On isn't enabled, so users have to authenticate twice: once to pass Azure AD pre-authentication, and once - on regular Umbraco login page.
When pre-auth is off, the HTTP requests sent when a user submits his credentials are:
But when pre-authentication is enabled, then the 2nd request fails with 401 response and with text message You do not have permission to view this directory or page.
You do not have permission to view this directory or page
Any idea what could cause this? How can I know whether this request hit Umbraco at all?
Umbraco version: 7.5.4 assembly: 1.0.6136.27241
Turns out, the EasyAuth mechanism used by Azure to provide pre-authentication for webapps isn't completely isolated from the webapps code:
Solved by adding this environment variable to the webapp, on its Configuration --> Application settings page:
Configuration --> Application settings
WEBSITE_AUTH_DISABLE_IDENTITY_FLOW = true
Then the Thread.CurrentPrincipal ASP.Net variable used by Umbraco code isn't affected by the EasyAuth. As said here, "this is designed to allow developers to protect access to their site with auth, but still have it use a separate login mechanism within their app logic".
is working on a reply...
Write your reply to:
Image will be uploaded when post is submitted