Question

Like SO, I am gonna depend on many Open ID providers to provide user authentication and I will use my own authorization methods. but I’m still in development phase, and don’t want to work with real OpenID providers currently, what approach can I use to test my users and their activities in the website (w/o TDD), to emulate real users but not really use Open ID providers.

No need to make auto-transfer of users into real OpenID servers (when moving to production mode) since the current users are just for testing purposes and Unit-test code.

I guess, I need a User Service layer which provides a higly abstracted way to deal with users, so that the move to the real Open ID providers can be smooth in the future and doesn’t affect the logic of my already written code.

Using C#.Net 4, ASP.Net MVC 3, Ninject

Answer 1

DotNetOpenAuth provides both server and client portions of OpenID and can be used to run your own OpenID provider for local testing.

• Give your site members their own OpenIDs with the provider support included in this library.

• Sample relying party and provider web sites show you just how to do it.