I'm looking for some guidance as to how to implement ASP.NET identity in a multi-tier environment. I have a physically separated presentation and business layer, but all of the examples and sample code I have seen for Identity all involve using EF right from the presentation layer to the DB. Instead of hitting the DB direct, I will have a set of WCF services as my business layer (pretty typical I'm sure). I'm good with using EF at the bottom as an ORM.
I am assuming the most straight forward approach would be to have custom implementations of IUser*Store interfaces, then those implementations would call the back-end web services.
Is this the recommended approach, or am I missing something? I guess the other approach is to push all of the identity code down to the business layer instead of the default presentation layer, but this seems heavier.