Orchard CMS User Membership

What is the preferred way to integrate a custom membership provider with Orchard?

I saw a couple of posts about introducing the new service IMembershipService and IUserService (from Orchard.Users), and then other modules, such as OpenAuthentication, that seem to do a lot more (but still using UserPart?).

We already have an ASP.NET membership provider, can it be integrated as?

+5
source share
1 answer

A custom implementation IMembershipServiceis the way to go if you don't want to use the default Orchard.Users module at all. Useful when you still want to do forms authentication, but just save auth data in a different place and not in UserPart.

, ( + ), IAuthenticationService.

, :

  • IMembershipProvider (/ )
  • IAuthenticationProvider (// ..).

.

auth, OpenAuth, , IIRC.

+7

All Articles