ASP.Net membership for desktop application - is it proper approach?
===

a colleague of mine suggested that we use ASP.Net membership for our new WPF desktop application in which we need users, roles etc. He suggests to encapsulate all database interaction in WCF REST service (so later on we can reuse it, let's say, for iPhone app), and then let desktop app to talk to it. This service will have `User/Login` function which will return cookie, and then this cookie will be used for the subsequent requests from the desktop app.

Is it proper approach/solution? Are there any articles which talk about pro and contra of this approach? Any other "out-of-the box" solutions I should consider?

Thank you.