I've been experimenting with the Members functionality in Um 5.1 (RC up to now), and specifically have been looking at howI can swap the default members provider out for a custom one (sourcing information from lots of places).
I initially did this by inheriting from MembersMembershipProvider, and swapped my replacement in via the config entries <membership> <providers> </providers> </membership>.
This has worked, and lets me intercept the GetUser call - but I think there must be a better way.
On gotcha with this approach, is I can not easily return a set of groups that the user is in (I have to map this to an Umbraco Member or User for that to work).
The other thing I was looking for, and failed to find, was a means of swapping out the provider that gets the data for the Members Back Office pages - ideally I'd like to turn this into a read only view on the external members data that we already hold ...
Umbraco 5.1 - Members
Hi folks,
I've been experimenting with the Members functionality in Um 5.1 (RC up to now), and specifically have been looking at how I can swap the default members provider out for a custom one (sourcing information from lots of places).
I initially did this by inheriting from MembersMembershipProvider, and swapped my replacement in via the config entries <membership> <providers> </providers> </membership>.
This has worked, and lets me intercept the GetUser call - but I think there must be a better way.
On gotcha with this approach, is I can not easily return a set of groups that the user is in (I have to map this to an Umbraco Member or User for that to work).
The other thing I was looking for, and failed to find, was a means of swapping out the provider that gets the data for the Members Back Office pages - ideally I'd like to turn this into a read only view on the external members data that we already hold ...
Any thoughts, pointers, etc?
Andy
is working on a reply...
This forum is in read-only mode while we transition to the new forum.
You can continue this topic on the new forum by tapping the "Continue discussion" link below.