When session variables are used in asp.net, okta authentication fails

[kiran]

Hi,
I am using Okta with asp.net web application. My application is using the default or built in authentication as well as okta. If I just use Okta login, it works good. However there is one weird issue, with the regular login (non okta), once user is authenticated, the application is using few session variables to store user specific information. Once session variables are used, Okta login fails, means when Okta user is doing login, in asp.net C# code HttpContext.User.Identity.IsAuthenticated always returns false

If I stop using session variables, it starts working !! This is really crazy. I have spent too much time on this

Can anyone help, Is it not possible to use session variables in asp.net while Okta + default authentication is used ?

Please help.

Thanks
Kiran

[Fuzzard]

hi Kiran, can you check if Chris’ solution from this older post is working for you as well?

OktaASP middleware not registering HttpContext Identity - Infinite Loop

Anyone who gets this issue with the Cookie not getting set in Forms authentication, the resolution was to override the default AutheticationType in the CookieAuthenticationOptions in the StartUp: app.UseCookieAuthentication(new CookieAuthenticationOptions() {AuthenticationType = “Cookies”, CookieManager = new SystemWebCookieManager() });

[kiran]

Hello @Fuzzard, Looks like the reference you have provided is referring to cookies, however I have issues with the net Session variables like Session[“abc”]

Thanks

[Fuzzard]

the update to the authentication type also seems to resolve the problem with adding separate session variables in my testing

with the default setup, HttpContext.User.Identity.IsAuthenticated returns false, while with that fix it returns true

[kiran]

Interesting!
I am testing this fix.

Thanks