Losing authenticated CurrentPrincipal after first "expand" in custom data service provider RRS feed

  • Question

  • Hello everyone,

    I am running a custom data service provider which replaces the GetSequenceValue method with its own code to provide the values (like in http://msdn.microsoft.com/en-us/data/gg191846).

    The service is hosted as a custom web service in SharePoint and Basic Authentication is enabled in IIS. Now when I access the service with an $expand call the first call to my GetSequenceValue the Threading.Thread.CurrentPrincipal is set to the user that did the basic authentication in the browser. But the second call for the next object has no authenticated user set. (The CurrentPrincipal has IsAuthenticated:False and no Name)

    The thread-id did not change in between.


    What is wrong here? At what point is the CurrentPrincipal reset and why is it happening before the OData call finished?




    Monday, July 25, 2011 1:29 PM