Question

What solutions have people come up with to develop their web applications offline when they made the decision to use OpenId for site membership?

Couple of ideas:

  1. Create two login pages one for OpenId and one for ASP.NET Membership
  2. Create local OpenId provider with test accounts

Any thoughts?

Was it helpful?

Solution

You could use an inversion of control container to contain your OpenID implementation and for a quick implementation you could use Moq to provide preconfigured responses.

OTHER TIPS

Just mock it!

I hardwire my login.aspx page to always do:

FormsAuthentication.RedirectFromLoginPage("http://blog.nerdbank.net/")

or something like that based on some variable. That way, I don't actually log in using OpenId but it looks to the rest of the web site like I did.

Just be sure to either revert the change, or make it based on some condition that is only true in development. :)

Licensed under: CC-BY-SA with attribution
Not affiliated with StackOverflow
scroll top