Custom membership provider broken after upgrade from 4.2 to

Posted by Community Admin on 04-Aug-2018 10:37

Custom membership provider broken after upgrade from 4.2 to 4.4

All Replies

Posted by Community Admin on 27-Jan-2012 00:00

Our custom membership provider doesnt work after upgrading to 4.4.

The provider is initialized by sitefinity but the ValidateUser method is never invoked when using 'Telerik.Sitefinity.Security.SecurityManager.AuthenticateUser'.

Instead it goes straight to GetUsers (which does return a list of valid Sitefinity Users) and returns a 'UserLoggingReason.Unknown'

Posted by Community Admin on 27-Jan-2012 00:00

Fixed by feeding the ValidateUser method a Sitefinity User instead of a username string.

http://www.sitefinity.com/devnet/forums/sitefinity-4-x/developing-with-sitefinity/sitefinity-4-3-broke-custom-membershipprovider.aspx 

The post was made in November of last year. In the post you mention that you forgot to include the changes in the change logs. It still isnt included!
This cost us 2 days!

Posted by Community Admin on 31-Jan-2012 00:00

Hi Erik,

I am sorry that this caused so much trouble. I suppose your custom provider doesn't have a GetUser() method implemented? We changed a bit the logic of the ValidateUser security method - it first calls GetUser() and if there isn't such a method or it returns null then the logic assumes that the validation fails. That's why you need to implement such method to return a valid User object.

Kind regards,
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

This thread is closed