How to make sure HttpContext.Current is not lost during IdentityServer notifications

Asked May 24 '19 at 18:43

Active May 25 '19 at 01:05

Viewed 393 times

I have a scenario where I am using a notification event in my client in the setup code is very simple as follows. This is a AspNet Mvc 4.72 client that uses AspNetCore IdentityServer4:

app.UseOpenIdConnectAuthentication(new OpenIdConnectAuthenticationOptions
{
    ClientId = "members",
    ...
    Notifications = new OpenIdConnectAuthenticationNotifications
    {

        SecurityTokenValidated = notification =>
        {
            ... 
            // Sometimes this is null but I have to make sure it is 
            // always available so I can initialize stuff here.
            HttpContext.Current.<Use context here>;
            return Task.CompletedTask;
        }
    }
});

Actually, more specifically I need access to the session state but it doesn't matter there are some other needs directly related. I am not really sure why this happens but from my research it has something to do with SynchronizationContext and the lifetime of a AspNet Mvc request.

If anyone has a definitive answer about how to ensure the HttpContext's existence please let me know.

edited May 25 '19 at 01:05

asked May 24 '19 at 18:43

jwize

4,230
1
33
51

You will have to clarify more about what kind of things you are using there. That is not ASP.NET Core. – poke May 24 '19 at 23:14
Please check https://stackoverflow.com/questions/18383923/why-is-httpcontext-current-null-after-await – user11775951 Jul 12 '19 at 13:51
worked for me – jwize Jul 13 '19 at 06:27

How to make sure HttpContext.Current is not lost during IdentityServer notifications

0 Answers0