indice-co/Indice.Kentico

Error when attempting to run in Azure App Service

Closed this issue · 1 comments

epuio commented

Hi,

I'm trying to get the Indice Kentico OIDC plugin to work in Azure with Kentico 12 (I've successfully gotten it running with IIS on a Windows system). When I connect to /SignIn.ashx, I'm redirected to the IDP successfully. However, once I enter my credentials and get redirected back, I get the following error in the browser:

`Server Error in '/' Application.
The resource cannot be found.
Description: HTTP 404. The resource you are looking for (or one of its dependencies) could have been removed, had its name changed, or is temporarily unavailable. Please review the following URL and make sure that it is spelled correctly.

Requested URL: /SignInOidc.ashx
`
I've tried to double check that I've got all of the necessary DLLs. I temporarily removed System.Text.Encodings.Web.dll to confirm that I get an explicit dependency error log, which I do (under Diagnose and solve problems --> Diagnostic Tools --> Support Tools --> Application Events on the app service). When I put the DLL back, I don't get any dependency errors.

However, I do get the following error in the log:

`4005
Forms authentication failed for the request. Reason: The ticket supplied was invalid.
2/16/2022 12:30:35 AM
2/16/2022 12:30:35 AM
6146c4ce543e4bddb3c26d84bda420d6
9
1
50201
/LM/W3SVC/769197253/ROOT-7-132894450124207552
Full
/
C:\home\site\wwwroot
pd0sdwk000G8T

13108
w3wp.exe
IIS APPPOOL\dev-sypw-1-102921-cognito
https://dev.syda.net:443/SignIn.ashx
/SignIn.ashx
35.142.159.41

False

IIS APPPOOL\dev-sypw-1-102921-cognito`

It appears that SignIn.ashx is successfully getting executed so that it redirects but simultaneously generating the above error. It doesn't appear that SignInOidc.ashx is getting executed.

Any ideas of what I might be doing wrong or a way that I can figure out what is causing the error. Thanks for any suggestions you can provide.

epuio commented

Never mind. It was a typo that I had overlooked. After I fixed this issue, however, I ran into another error that showed that I had left some Windows-specific logging messages in the code I submitted to you all. I will submit updated code via the previous process.