@spike83 I do not want to add a member to IDocumentMaterializer if we can avoid it. You can achieve the same effect in your project by making a derived class of EntityFrameworkDocumentMaterializer that uses constructor injection of IPrincipal, and it wouldn't require any interface changes in the main library.

@csantero ok. How and where would you register the principal?

@spike83 In my project I do something like the following using Autofac and Owin:

            builder.Register(ctx => HttpContext.Current.GetOwinContext()).As<IOwinContext>();

            builder
                .Register((c, p) =>
                {
                    var owin = c.Resolve<IOwinContext>();
                    return owin.Authentication.User;
                })
                .As<IPrincipal>()
                .InstancePerRequest();

Then you can just inject IPrincipal into any request-scoped class's constructor, such as the document materializer.

@spike83 do the OnCreate etc. methods need to return the same record they were passed in? It seems to me they could just return Tasks.

Thanks!