|
|
Rank: Addict
Joined: 3/17/2008
Posts: 982
Location: Nyborg, Denmark
|
I'm looking at stripping down the membershipprovider support for v3 to make the release closer. Here's what's working now and then my ultimate thoughts for future support. Let me know what you think.
What's supported in next commit:
An umbraco MemberShip and profileProvider. This means that you can use standard login/forgotpassword/profile support in .NET with umbraco member data. It also means that 3rd party controls that rely on the membership and profile providers in .NET 2.0 will support umbraco members out of the box.
What I wanted initially:
Full support for existing providers in umbraco. The idea was that the membership functionalities in umbraco should simply be a wrapper for the .NET membership and profile providers. This way you could use existing providers with umbraco, and as such easily integrate your own membership and profile providers with umbraco (like using your own authentication methods or external storage outside umbraco). It seemed pretty straightforward at first and went really well. However loads of challenges came up and it quickly became clear that of this shouldn't cause a long delay in v3 it would be either a compromise on backwards compatibility (not an option) or a configuration hell (which would lead to many confusions and low adoption).
Why would support for external providers be so neat:
Because it could make it very easy to use 3rd party authentication and member systems while still have the joy of the umbraco user interface and api's to configure them. Like using the "Public Access" to control access to pages even though you use your own authentication system instead of umbraco members. Or use LDAP/Active Directory as authentication for the umbraco web client (/umbraco).
So what am I saying:
I'm saying that there'll be providers for .NET membership and profiles for umbraco, but not support for external providers inside umbraco for v3. I really need to get v3 shipped and while provider support is a very really nice enhancement, it's not crucial. Especially if it ends up being implemented an inelegant way to speed up release. So it'll come in vNext (3.1), and until then there'll be no out-of-the-box support for external providers. However - as today it'll still possible to use external authentication tools, it just requires some degree of coding.
Hope you guys understands - the good news is this will make v3 very close to final beta.
Cheers,
Niels...
Jeeeez, did I really start this :-)
|
|
Rank: Aficionado
Joined: 8/12/2006
Posts: 139
Location: Norway
|
I'm surprised nobody has replied on this post... This feature is very important in a case I'm working on where we need SSO between multiple Umbraco sites. If excluded from v3, will the feature appear in a later release?
Kenneth Solberg - xeed* - core dev - level 2 cert pro - my blog
|
|
Rank: Addict
Joined: 3/17/2008
Posts: 982
Location: Nyborg, Denmark
|
Kenneth wrote:
I'm surprised nobody has replied on this post...
Me too! [quite=Kenneth] This feature is very important in a case I'm working on where we need SSO between multiple Umbraco sites. If excluded from v3, will the feature appear in a later release? [/quote] It will appear in v3.1 as I agree it'll make integration much easier and sweeter. However only if implemented in a way that makes it easy and intuitive to use. That was why I decided to strip it out of v3, as it would either be a crummy implementation or more v3 delay (which really, isn't an option is it ;-)) Cheers, Niels...
Jeeeez, did I really start this :-)
|
|
Rank: Fanatic
Joined: 3/15/2007
Posts: 378
Location: Cary, NC USA
|
Niels - we're looking into replacing our current proprietary 1.x architecture with Umbraco for 35+ sites and 15,000+ members. We're possibly looking to start our web apps port sometime this summer (2007). I know your trying to stay away from providing hard release dates but do you anticipate the 3.1 release anytime near the summer timeframe? Also, say we do use the Umbraco 3.0 architecture and have all of our accounts, groups and permissions created, will there be issues when upgrading to the 3.1 .NET membership provider? Many thanks in advance.
|
|
Rank: Addict
Joined: 3/17/2008
Posts: 982
Location: Nyborg, Denmark
|
John Hodgkinson wrote:
Niels - we're looking into replacing our current proprietary 1.x architecture with Umbraco for 35+ sites and 15,000+ members. We're possibly looking to start our web apps port sometime this summer (2007). I know your trying to stay away from providing hard release dates but do you anticipate the 3.1 release anytime near the summer timeframe? Also, say we do use the Umbraco 3.0 architecture and have all of our accounts, groups and permissions created, will there be issues when upgrading to the 3.1 .NET membership provider? Many thanks in advance.
Hi John! No, I won't give any promises (been there - quite a no-success ;-)) but I would assume that a release of v3.1 to be realistic end of the summer. Upgrade from v3 to v3.1 will be a no-brainer and if you've been using a .NET 2.0 MemberShipProvider while developing with v3, umbraco v3.1 will be able to use that out of the box (more or less - maybe a little web.config gym will be needed). Hope this helps - when v3 is excepted I hope to answer more specifically! /n
Jeeeez, did I really start this :-)
|
|
Rank: Fanatic
Joined: 10/9/2006
Posts: 460
Location: batavia, IL
|
and that more specific answer would be???? :) Just looking forward to v3 release....
bootnumlock - aka bob baty-barr My Packages Site: http://packages.maliciousthinktank.comBusiness Blog: http://www.maliciousthinktank.com/blogPersonal site: http://www.baty-barr.comLevel 1 Certified!
|
|
Rank: Fanatic
Joined: 3/15/2007
Posts: 378
Location: Cary, NC USA
|
Niels Hartvig wrote:
Upgrade from v3 to v3.1 will be a no-brainer and if you've been using a .NET 2.0 MemberShipProvider while developing with v3, umbraco v3.1 will be able to use that out of the box (more or less - maybe a little web.config gym will be needed).
Niels - so are you saying that if we use the current 3.0 Umbraco membership OR a .NET 2.0 Membership Provider integrated w/ Umbraco 3.0 - either way the membership upgrade from 3.0 to 3.1 should be a no-brainer? just want to make sure I'm understanding fully. Many thanks.
|
|
Rank: Newbie
Joined: 8/21/2007
Posts: 17
|
I thought I'd chime in and tell you that I agree 100%.
* Better to be done late than done poorly
* Nice, Nifty, but Not Critical
* Should Not have held up the last release
I already have a membership and profile system built for our website and would love to be able to integrate these users with content membership. However, we can certainly find temporary workarounds to accomlish whatever comes up with that regard.
Appreciate the attention to timelines
|
|
Rank: Devotee
Joined: 9/12/2007
Posts: 58
Location: Honoluu, HI
|
When do you plan on releasing v 3.1?
|
|
|
Guest |