I\'m looking to write a config file that allows for RESTful services in WCF, but I still want the ability to \'tap into\' the membership provider for username/password authe
Before you continue down this path of fighting to implement REST over WCF, I suggest you read this post by Tim Ewald. I was especially impacted by the following statement:
I'm not sure I want to build on a layer designed to factor HTTP in on top of a layer that was designed to factor it out.
I've spent the last 12 months developing REST based stuff with WCF and that statement has proven itself to be so true over and over again. IMHO what WCF brings to the table is outweighed by the complexity it introduces for doing REST work.