It seems to be a common practice to have the domain model for a web/client application in a separate class library. This enables me to provide both, a client application (WPF / WinForms) and a web application leveraging ASP.NET. Since there exists already a great solution to have users, roles and claims with the ASP.NET Identity Framework, it would not make any sense to re-implement this solution for the web part.
Unfortunately, this hinders me to create a common domain model class library for both, web application and client application since I need to be able to reference User and Role objects in my domain model (e.g. associate a customer object with an user object). I am now looking for a recommended way to be able to separate the ASP.NET Identity Framework from my domain model?