+1-888-365-2779
Try Now
More in this section

Forums / Bugs & Issues / Homepage redirected to login page for anonymous users

Homepage redirected to login page for anonymous users

3 posts, 0 answered
  1. FIMS Computing Services FIMS - UWO
    FIMS Computing Services FIMS - UWO avatar
    9 posts
    Registered:
    16 Dec 2005
    26 Oct 2009
    Link to this post
    After I upgraded from version 3.6 to version 3.7, anonymous users are being redirected to the login page.

    The home page has 'Anonymous access' set to Allow and before the upgrade we had no problems with anonymous users.

    Has something changed in version 3.7 SP1 that would cause this?

    Thanks
    Charles
  2. Ivan Dimitrov
    Ivan Dimitrov avatar
    16072 posts
    Registered:
    09 Dec 2016
    26 Oct 2009
    Link to this post
    Hi FIMS Computing Services FIMS - UWO,

    Try saving the page and resetting the permissions. If the problem persists, please open a support request and provide some more information about the problem. You can also send user credentials for the website backed, so that we could see this behavior.

    You could also create a simple test by creating a new home page, without any controls or custom scripts and see whether you will be redirected to the login screen. It is possible that you have some custom control that could check for anonymous user. Make sure that your authentication node looks as shown below:

    <authentication mode="Forms">
    <forms name=".ASPNET" loginUrl="~/sitefinity/login.aspx" protection="All" timeout="1440" path="/" />
    </authentication>
    <authorization>
     <allow users="?" />
    </authorization>


    Greetings,
    Ivan Dimitrov
    the Telerik team

    Instantly find answers to your questions on the new Telerik Support Portal.
    Watch a video on how to optimize your support resource searches and check out more tips on the blogs.
  3. FIMS Computing Services FIMS - UWO
    FIMS Computing Services FIMS - UWO avatar
    9 posts
    Registered:
    16 Dec 2005
    26 Oct 2009
    Link to this post
    I figured out the problem. It turned out it had nothing to do with the upgrade from 3.6 to 3.7 but the upgrade from IIS 6 to IIS 7 that I did at the same time.

    Thanks for the help.

    Charles
Register for webinar
3 posts, 0 answered