We don't want to use AspNetCompatibility mode in case we ever want to take advantage of net.tcp or another custom binding, so is there a way to specify and implement impersonation (read: userName=,password=) on the WCF Service Host side? Did Microsoft in their infinite wisdom leave this out? I posed this question to my friend Dru today after we were having trouble finding a way to do it. So there are plenty of articles on WCF Impersonation out there, but nearly all of them originate from the client...