Membership Provider - General Discussion

New Community Website

Ordinarily, you'd be at the right spot, but we've recently launched a brand new community website... For the community, by the community.

Yay... Take Me to the Community!

Welcome to the DNN Community Forums, your preferred source of online community support for all things related to DNN.
In order to participate you must be a registered DNNizen

Home All Forums

1
2
3
4
5

3/12/2009 12:31 PM

forest1

Joined: 3/12/2009

Posts: 2

Membership Provider

I was looking at some documentation that seemed to say that the PortalID mapped to the Membership Provider
ApplicationName but it looks as though ApplicationName is always set to the setting in web.config, DotNetNuke
by default.

Could someone point me in the right direction to understand how Users map to Portals via the Memberhip Provider
while the ApplicationName stays constants please.

Thanks

Mike

3/12/2009 1:37 PM

Brandon Haynes Haynes

brandonhaynes.org
Joined: 2/6/2006

Posts: 1172

Re: Membership Provider

Hi Forest1,

The ASP.NET membership application name is always "DotNetNuke" (by default), and is not used to partition users across portals in any way. DotNetNuke users are mapped to ASP.NET membership users via the Users table, via the username key. Users are mapped to portals via the UserPortals many-to-many associative table.

Hope this helps!

Brandon

Brandon Haynes
BrandonHaynes.org

3/13/2009 4:43 AM

forest1

Joined: 3/12/2009

Posts: 2

Re: Membership Provider

Brandon

Many thanks for your reply

I think I picked up some early documentation that suggested ApplicationName was to be used but I'm
glad to hear it isn't as there is a note for Membership.ApplicationName saying it isn't threadsafe.

Thanks again

Mike

3/13/2009 8:12 AM

Brandon Haynes Haynes

brandonhaynes.org
Joined: 2/6/2006

Posts: 1172

Re: Membership Provider

forest1 wrote

I think I picked up some early documentation that suggested ApplicationName was to be used...

I wouldn't be surprised at all if this is the case (and indeed I also have vague recollections about this being investigated) -- this would be a stronger overall design choice. However, there must be a (significant) design requirement that prevented this method from being used and the Users/UserPortal scheme implemented instead. One obvious limiting factor would be the fact that cross-portal host accounts would be made much more difficult in this sort of setup.

Anyway, hope your membership provider adventures go well!

Brandon

Brandon Haynes
BrandonHaynes.org

Page 1 of 1

These Forums are dedicated to discussion of DNN Platform and Evoq Solutions.

For the benefit of the community and to protect the integrity of the ecosystem, please observe the following posting guidelines:

No Advertising. This includes promotion of commercial and non-commercial products or services which are not directly related to DNN.
No vendor trolling / poaching. If someone posts about a vendor issue, allow the vendor or other customers to respond. Any post that looks like trolling / poaching will be removed.
Discussion or promotion of DNN Platform product releases under a different brand name are strictly prohibited.
No Flaming or Trolling.
No Profanity, Racism, or Prejudice.
Site Moderators have the final word on approving / removing a thread or post or comment.
English language posting only, please.

Products

Solutions

Resources

Partners

Community

Blog

About

QA

Ideas Test

New Community Website

DNN Corp. (DotNetNuke)