Hi folks. We are creating a fairly large B2C portal that will ultimately contain 15-25k user accounts. These accounts currently exist in a line of business (LOB) app which is exposed to DNN via a web service. I am creating an authentication provider to determine if  the username/password exist in the LOB app and then determine if a matching DNN account exists. If the DNN account does not exist then the provider will create the DNN account (via the DNN API). Here are some more details:

- the DNN portal user will never interact/view his/her DNN account
- the DNN account will contain just a few properties and a few Role assignments
- the DNN account will be used primarily as a way to display relevant content (via role membership)
- all user data (address, account, etc.) will be accessed via web service calls to the LOB app

Given the above, it appears we have a choice re the reciprocal DNN accounts:
 
A) we could create 1:1 DNN user accounts (i.e., for every LOB account, create a matching DNN account when the user logs in (if it doesn't exist))
B) we could create 10-20 "proxy" accounts and based on the LOB user data, map the user to the appropriate DNN account (i.e., at any one time we may have 100 or so users logged into the same DNN account ("SubscriberABC", "SubscriberXYZ", etc.).

Are there any disadvantages to the proxy-account idea?

Thanks!