U4-1659 - New Member API

Created by Morten Christensen 07 Feb 2013, 08:54:50 Updated by Shannon Deminick 25 Mar 2014, 00:20:54

Parent for: U4-1983

Parent for: U4-1984

Parent for: U4-2958

Parent for: U4-3208

Parent for: U4-3886

Parent for: U4-3887

Parent for: U4-3888

Parent for: U4-3889

Parent for: U4-3890

Parent for: U4-3891

Parent for: U4-3893

Parent for: U4-3902

Parent for: U4-3903

Parent for: U4-3904

Parent for: U4-3975

Parent for: U4-3996

Parent for: U4-3997

Parent for: U4-4106

Parent for: U4-4107

Parent for: U4-4120

Parent for: U4-4121

Parent for: U4-4122

Parent for: U4-4123

Parent for: U4-4227

Parent for: U4-4255

Parent for: U4-4256

Parent for: U4-4257

Parent for: U4-4260

As part of the effort to introduce a new public api we'll introduce a new member api, which will be consistent with the new models and services (ie. Content and ContentService).


Randy McCluer 26 Feb 2013, 22:42:26

This isn't on the Roadmap for 6.1 anymore is it?

Morten Christensen 27 Feb 2013, 06:52:45

Yup, it is. What are your thoughts?

Randy McCluer 27 Feb 2013, 15:50:58

Is this going to be in Core/Services/MemberService or on the MemberProvider? Will we be able to query for members by profile field values?

Morten Christensen 27 Feb 2013, 15:57:34

There will be a MemberService, which we will use when creating a new MembershipProvider impl. so all of the old obsoleted code won't be used anymore. I haven't gone into details regarding the methods that the MemberService will expose, so I'm open to suggestions. Querying by field values is a bit tricky, but should be able to make it work. I have been thinking about saving some of the standard membership provider properties by convention as Member properties along the lines of "umbracoNaviHide", "umbracoUrlAlias" etc. But just a thought so far. Will dive into it in a week or two from now.

Randy McCluer 27 Feb 2013, 16:13:09

Querying by fields seems pretty important. I know that might be tough to integrate that into the aspnet membership provider model, but I'll be glad to help kick the tires. I was thinking we were a little closer to 6.1, and was wondering if I just wasn't seeing the code, but with an April target, makes sense.

Sebastiaan Janssen 21 Mar 2013, 17:21:19

Unfortunately, due to more pressing issues cropping up recently we will not have enough time to introduce this issue in the upcoming 6.1.0 release. Therefore, we're moving it to the 6.2.0 release.

Jeroen Breuer 02 Sep 2013, 06:34:31

Will there also be a new way to get the member cached? Currently I still use [library.GetMember|http://our.umbraco.org/forum/developers/extending-umbraco/27626-Accessing-Member-Information#comment103415] because it's cached, but I would prefer something like Umbraco.TypedMember which you can also do for Content and Media: http://our.umbraco.org/documentation/Reference/Mvc/querying.

Vincent Baaij 02 Sep 2013, 14:24:51

Will the new API work with the Asp.Net SimpleMembership provider? If so, it would make it easier to use external providers (like Facbook, Twitter, etc.). In a standard MVC 4 applicationt this can be turned on when creating a new project. Would be nice if an Umbraco site could hook in on that mechanism.

Yannick Smits 17 Sep 2013, 17:51:25

for inspiration: http://umembership.codeplex.com

Petr Snobelt 03 Mar 2014, 13:15:01

+1 to integrate OData authentications for users and members. You can look at new http://www.asp.net/identity which should replace old identity provider, or custom implementation - https://github.com/brockallen/BrockAllen.MembershipReboot

Petr Snobelt 12 Mar 2014, 15:12:52

I also create sample how to integrate Oauth to login https://github.com/PetrSnobelt/UmbracoOAuthLogin

Priority: Normal

Type: Feature (planned)

State: Fixed

Assignee: Shannon Deminick

Difficulty: Normal

Category: Architecture

Backwards Compatible: True

Fix Submitted:

Affected versions:

Due in version: 6.2.0


Story Points: