Error in renaming custom membership provider - Sitefinity - Front- & Back-End Development

All Replies

Posted by Community Admin on 19-Jul-2011 00:00

Hi,

Here is the flow:
1. create custom membership by inheriting OpenAccessMembershipProvider
2. configure it on Administration->Settings->Advanced->Security->Membership Providers (placed a name and type)
3. add a user on the custom membership provider, rebuild site
4. user successfully logged in
5. rename the custom membership provider, rebuild site
6. successful, the new name appear now on Add User and Login dropdown
7. logout, and re login is successful
8. view users on custom provider (can't view)
9. logout, and re login (unsuccessful), prompt says
"Someone is already using this username and password from another computer or browser.
To proceed, you need to log him/her off"
when I click "Log the other user and enter" button, yellow screen of death error.

There is no configuration for data provider with the name of "CustomProvider" for "Telerik.Sitefinity.Security.UserManager" manager. Please check the spelling of the name and whether such configuration exists.

I observed SF do not update sf_manager_info and sf_lic_user_activity tables when renaming custom membership provider. I edited them manually and error was not encountered anymore.

Posted by Community Admin on 21-Jul-2011 00:00

Hi Rc,

The old name of the membership provider is saved in a table named sf_lic_user_activity. Since you renamed the provider you will need to manually delete the record in this table that has the column provider_name = 'CustomProvider'

Best wishes,
Lubomir Velkov
the Telerik team

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 Public Issue Tracking system and vote to affect the priority of the items

Posted by Community Admin on 15-Dec-2011 00:00

We've fixed this exact same issue: Within IIS - you can only have Forms + Windows authentication turned on for a secure folder so that you don't have to provide the domain name during the authentication challenge.
Apparently with Sitefinity 4.3, if you provide the domain name during authentication, they look for a configuration entry to match the domain name - no idea why and what a hassle to figure out; hope this helps!

This thread is closed