Following are three examples describing when to use which provider. Note that every use case has its own special requirements in terms of security, databases, platforms, etc.
You have a custom database, which is already utilizing the SqlMembershipProvider functionality. In this case, you can add a new provider to your provider’s collection inside your Sitefinity CMS instance, and point to this database. After that, the provider is fully functional.
In this case, you are implementing an SqlMembershipProvider.
You have an existing application, which has its own security mechanism, such as a CRM system, a PHP/MySQL web application, or a REST WebAPI that is used for authenticating customers.
If you want, for example, to let customers login to a specific part of your website, perform the following:
In this case, you are implementing a custom MembershipProvider.
You want all the functionality described in Case 2 above, but you also want to add the following:
In this case, you are implementing a custom Membership Provider, which inherits the MembershipDataProvider class that comes with Sitefinity.
Back To Top
To submit feedback, please update your cookie settings and allow the usage of Functional cookies.
Your feedback about this content is important
Copyright © 2022 Progress Software Corporation and/or its subsidiaries or affiliates.
All Rights Reserved.
Progress, Telerik, Ipswitch, and certain product names used herein are trademarks or registered trademarks of Progress Software Corporation and/or one of its subsidiaries or affiliates in the U.S. and/or other countries. See Trademarks for appropriate markings.
Powered by Progress Sitefinity