Hi,

I plan to use DNN in a portal application which will be used by many users (max 1/2 million). This portal will complement an existing windows application which will have these users already created and managed. It's not productive/efficient for the site admin to create/manage dnn users for each and every user.  

My plan is to have 1 single DNN user and when a web user logs in we will validate him and sign him in to the portal as that 1 single dnn user. The DNN user is chosen ahead of Unauthenticated users since I'd be able to use more DNN features and also its slightly better security model. 

My question is what are the problems/limitations you would notice with this approach?

Eg : - Will DNN be able to seperate out each instance of the same DNN user (When multiple ppl is logged in)?

      - Is there any higher limit on the number of users I can have in this approach?

Feedback is much appreciated.

Regards,

Uchitha

Hi,

Sorry for the late response. In my solution I will implement all the dnn modules I need for normal users. But for Admin I will reuse what ever comes with DNN.  So I will develop a custom login module which will talk to my legacy application and validate users on the fly. This means that at any given moment there could be 100 instances of the same dnn user being logged in to portal (as different business users according to my legacy app).

My doubt is how will DNN handle this? Will it be able to differentiate every one of them still (Provided userId is not used in my modules).

Is there any known upper limit to the number of users that can log in like this?

Uchitha.

 I thank you both for enlightening me. I will look in to the membership provider pattern a bit and come back to you, hopefully with good news.

Uchitha.