Products

Solutions

Resources

Partners

Community

Blog

About

QA

Ideas Test

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

HomeHomeUsing DNN Platf...Using DNN Platf...Administration ...Administration ...all users getting setup with applicationName DotNetNukeall users getting setup with applicationName DotNetNuke
Previous
 
Next
New Post
4/19/2007 11:59 PM
 

all my users are setup associated to the application of "DotNetNuke" wasnt a problem until 4.5 now they need to be associated to their individual portals so two portals can have a 'bob' user if they want. I thought the DNN team set it up so the PortalID would be attached to the applicationName in the web.config so you wouldnt have this conflict. Thats what it sounded like the DotNetNukeMembership.pdf doc was saying that came with 4.4

am i missunderstanding how this works?

help, and thank you.

 
New Post
4/20/2007 12:42 AM
 

allow me to clarify, under my current install, 4.0.2 of DNN all the users are associated to the proper ApplicaitonID , which is their portal, apparently during the upgrade to 4.5.1 they are all being converted to the DotNetNuke applicationID from the webconfig. I dont understand why this is the case i thought they were able to add the portalID as the suffix to the applicaiton name as describe in the white paper, quote:

"The Membership provider has a concept of ApplicationName which can be used to
partition data for different applications or sites. In the original API implementation, the
ApplicationName value had to be stored as a static value in the web.config file. This
model locks down the ApplicationName to a single data store per IIS account – a model
which does not support the multi-portal requirements of DotNetNuke.
In depth discussions of this issue revealed no viable workarounds to the multi-portal
dilemma and as a result, Microsoft logged a Design Change Request ( DCR ) in their
system to have the ApplicationName feature modified so that it can be specified
dynamically per request ( this requires that the ApplicationName property be threadsafe,
etc… ). The DCR went through various review committees and was ultimately
approved for inclusion in Whidbey Beta 2. In addition, the logic was integrated into the
backported Membership provider for ASP.NET 1.1.
Once the ApplicationName was available for dynamic specification, it was used on a
request basis for identifying the current PortalID. The process involved adding the
PortalID as a suffix to the ApplicationName specified in the web.config ( ie. DotNetNuke-
0 ). The prefix is important in the deployment scenario where you are using a central
Membership data store for multiple IIS accounts."

 

 
New Post
4/21/2007 2:33 PM
 

so if my requirement is to have a 'Bob' user for more than one portal with different passwords, that means i have to right my own custom membership provider? has anyone done that yet? i find it hard to believe that I am the only one with this requirement. we setup portals for different customers. any thoughts are helpful, even just to confirm my thinking on the way this is all working...

 
New Post
1/26/2008 4:27 AM
 

It's very interesting! Have you find the solution? thanks

 
Previous
 
Next
HomeHomeUsing DNN Platf...Using DNN Platf...Administration ...Administration ...all users getting setup with applicationName DotNetNukeall users getting setup with applicationName DotNetNuke


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:

  1. No Advertising. This includes promotion of commercial and non-commercial products or services which are not directly related to DNN.
  2. 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.
  3. Discussion or promotion of DNN Platform product releases under a different brand name are strictly prohibited.
  4. No Flaming or Trolling.
  5. No Profanity, Racism, or Prejudice.
  6. Site Moderators have the final word on approving / removing a thread or post or comment.
  7. English language posting only, please.
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out