views:

55

answers:

3

I have an application that works great on localhost with forms authentication.

I deployed it to the deployment machine and it to the build machine and received and endless set of 302 redirects.

I try logging onto the deployment machine and access the page via the deployment machines ip and it works again.

So it is not working when I try and access the site from my computer to the build computer.

What could be causing this?

A: 

There's most likely an IIS configuration issue.

  • Determine that your Authentication is set to allow anonymous.
  • Ensure your default page is specified in the list in IIS.
p.campbell
I don't think I specity a default page.... authentication is set to allow anonymous....
zachary
+1  A: 

I had this problem a few weeks ago. My problem was that my Default.aspx required roles/permissions that the user I was trying to log with did not have.

Default.aspx (anonymous user) -> Login.aspx -> [logged in] -> Default.aspx (user denied access) -> automatic redirect to the main page -> Default.aspx (user denied) -> endless loop.

I fixed it by removing any permissions required for my default page and making sure the permissions in my web.config were Ok.

Rafael Belliard
I'm not sure what this means.. I am redirecting to a page (that is not default) and it needs to be protected for deny anonymous....
zachary
@zachary what i mean is that make sure your default page (whatever that is) does not require a security role the logged user is not in.
Rafael Belliard
I'm not using roles... so I am assuming I am ok on this point....
zachary
A: 

And it was because the time on the server was different then the time on my client machine. Who knew such a thing could happen? Not me.

The sad part is I changed the time hours ago but I put it at AM instead of PM. Awesome!

zachary