There's an odd issue when you try to use Passport on Windows Server 2003 - basically, the default 'Secure Level' of Passport is 10, unfortunately if you don't use SSL this means Passport won't work correctly for you. In .NET this manifests itself as the Passport scarab showing you as logged in but if you try Context.Identity.User.IsAuthenticated, it'll always return 'false'. Now, I know what you're thinking, just change it to '0'...umm...nope, the default Passport Administration tool installed with Windows Server 2003 won't let you change this...and you can't (well not in any way that I've found so far) upgrade to 2.5 (appears to...but the admin utility doesn't change...). So, you have two options (well three, but ignoring it rarely works...), either change the registry key (described here) - or connect to your server from a machine with Passport SDK 2.5 installed (from the admin tool) and change it that way. I have to say, the support for Passport is pretty rotten - as is the SDK and support on Server 2003 (which really is unacceptable IMHO). I've said before, this is a pretty nice system when it works but no-one is going to adopt it when it's so pernickety and costs so damn much ($10,000 a year last I checked)! Come on, what about a developer / community type license? Also, when is .NET Passport 3.0 actually going to arrive (the fabled Web Services enabled Passport)?