Back to list
Views:   0
Replies:  0
Anyone else experiencing this?
Sep 16, 2015
Reply 1
My fix for this was assigning  HttpContext.Current.User = customPrincipal; in the Application_PostAuthenticateRequest() method in the global.ascx, instead of assigning it to the current thread's principal.  Using the current thread's principal just wasn't a reliable approach since I was intermittently getting nulls back for the CurrentUser properties for identical request.  Obviously I had to update the CurrentUser class to use HttpContext.Current.User, rather than Thread.Current.Principal. 
Mark Erasmus, Sep 17, 2015
Stay Inspired!
Join other developers and designers who have already signed up for our mailing list.
Terms     Privacy     Licensing       EULA       Sitemap      
© Data & Object Factory, LLC.
Made with    in Austin, Texas