The web.config file uses forms authentication for ALL pages within the 
web. So the REGISTER link doesn't load the new.aspx page but instead 
reloads the login.aspx page looking to authenticate. Shouldn't the 
new.aspx page bypass the forms authentication? If so, how?

Thanks!
Ryan Stevens

> The web.config file uses forms authentication for ALL pages within the 
w> eb. So the REGISTER link doesn't load the new.aspx page but instead 
r> eloads the login.aspx page looking to authenticate. Shouldn't the 
n> ew.aspx page bypass the forms authentication? If so, how?

> Thanks!
R> yan Stevens

************************

Found it.

The web.config needs an authorization list.

The authentication is set to Forms and protects all pages.

To specify pages that are not protected the following xml does the trick.
_____________________________________________
<location path="Modules/Users/New.aspx">
<system.web>
<authorization>
<allow users="*" />
</authorization>
</system.web>
</location>
______________________________________________

Place authorizations after the existing </system.web> tag.

Ryan Stevens