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

Forums / Bugs & Issues / Authentication Provider drop down disappeared after upgrade

Authentication Provider drop down disappeared after upgrade

3 posts, 0 answered
  1. Noah
    Noah avatar
    5 posts
    Registered:
    19 Feb 2013
    11 Apr 2014
    Link to this post

    We are upgrading a client from Sitefinity 5.0 to 6.3. We have completed the upgrade on the test server and during testing a user pointed out that the drop down that used to appear on the login screen for the backend that allowed them to specify their authentication provider is not on the login form anymore.

     What do I need to do to get it back?

     I have verified that the 3 providers in use are still listed under Membership Providers.

  2. Ivan D. Dimitrov
    Ivan D. Dimitrov avatar
    310 posts
    Registered:
    26 Mar 2015
    14 Apr 2014
    Link to this post
    Hello Noah,

    This is indeed not default behavior. The membership providers are configuration settings that do not get affected during an upgrade procedure. What you can try is to restart the application and see if the dropdown will be present on the login page. Alternatively you can also recreate your providers. Provided this is not an option for you, I can suggest you open a support ticket where the issue can be investigated in further detail.

    Regards,
    Ivan D. Dimitrov
    Telerik
     
    Do you want to have your say in the Sitefinity development roadmap? Do you want to know when a feature you requested is added or when a bug fixed? Explore the Telerik Sitefinity CMS Ideas&Feedback Portal and vote to affect the priority of the items
     
  3. Noah
    Noah avatar
    5 posts
    Registered:
    19 Feb 2013
    16 Apr 2014 in reply to Ivan D. Dimitrov
    Link to this post

    Thanks for the response. I went to delete the membershipprovider and re-add it and I realized that for some reason the "providertype" field was empty. Some how it must have been cleared during the upgrade. I copied the value from our production instance to the one we are testing the upgrade and it worked.

3 posts, 0 answered