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

HomeHomeOur CommunityOur CommunityGeneral Discuss...General Discuss...How can I share the user list with another website, which also uses ASP.Net 2.0 Membership?How can I share the user list with another website, which also uses ASP.Net 2.0 Membership?
Previous
 
Next
New Post
10/5/2006 1:54 PM
 

I am developing a website using ASP.Net 2.0, which needs a forum. I have just set up a DNN site, & am starting to get my head around how it works. The main site also has a user registration process, which I have implemented using the ASP.Net 2.0 Membership facility, using the standard SQLServer provider.

The users of this site will really hate having to rehgister twice, so I need some kind of mechanism to either (i) share the user information, so that users regietered in one are automatically registered in the other, or (ii) automate the registration process in the other, so the two user exists in both.

My first idea seems preferable to me, unless of course it raises many issues, in which case it may be simpler to implement my second idea. However, let's think about the first idea first.

Firstly, what would happen if I simply pointed my other website's membership provider at the DNN database on my SQL Server? Has this been done before?

I notice that DNN doesn't implement the ASP.Net 2.0 Roles functionality, whereas my other website does. If I pointed both websites (the DNN one & the non-DNN one) at the same SQWL database, but then enabled roles in my other website, would that just enable my other website to use the Roles tables in the DNN database, even though DNN doesn't use them itself? Would that then enable me to use these Roles exclusively in the other website, without affecting any Roles functionality within DNN (given that DNN implements its own Roles functionality)?

Any thoughts on this topic would be appreciated, as I need to decide quickly exactly how I am going to do this, as I am very short on time (but then, aren't we all, most of the time?)

Thanks,

Paul Cutcliffe
eNet IT Solutions Ltd
+44 (0)1323 640500
+44 (0)7739 731427

 
New Post
10/6/2006 5:10 AM
 

Well in the absence of any advice, I guess I'll just have to try it.

I'll create another instance of both, each pointing to the same database, & see what happens.

 
New Post
10/6/2006 8:06 AM
 

I'm finding new ApplicationIDs appearing in my tables, even though none of my web.config files specify anything other than applicationName="/", including the DNN one.

 
New Post
10/9/2006 1:35 PM
 

My aim was to share a user database between an ASP.Net 2.0 (non-DNN) website and a DNN (4.x) ASP.Net 2.0 website, so that users would have consistent usernames & passwords. I did this by simply extracting the files to a folder, editing web.config so that the settings were more consistent with the other website (Clear passwords & a few other changes), then running the DNN installation.

The main website allows anyone to register, but the DNN site is only for a subset of those users, selected by the website administrator. So I disabled Registration in DNN (set Registration to None in Site Settings), & created a View in the database that shows users in ASP.Net's aspnet_Users who are not in DNN's Users table:

SELECT     TOP 100 PERCENT dbo.aspnet_Users.LastActivityDate, dbo.aspnet_Users.UserId, dbo.aspnet_Users.UserName, dbo.aspnet_Membership.Password, 
                      dbo.aspnet_Membership.Email
FROM         dbo.aspnet_Users INNER JOIN
                      dbo.aspnet_Membership ON dbo.aspnet_Users.UserId = dbo.aspnet_Membership.UserId LEFT OUTER JOIN
                      dbo.Users ON dbo.aspnet_Users.UserName = dbo.Users.Username
WHERE     (dbo.Users.Username IS NULL)
ORDER BY dbo.aspnet_Users.LastActivityDate DESC

I created an admin page that shows this view, as well as a button that adds the users to DNN's Users table.

One outstanding issue is that the newly enabled users don't get assigned the 'Registered Users' role, but other than that, they seem just the same as if they had registered on the DNN site directly.

 
New Post
10/10/2006 5:40 AM
 

Why woludn't you just create some API in your DNN application (web service or some global assembly)
which will be called from the other application (each time new user is being registered),
that API will simply insert the new user details into DB (using or not using the membership provider).

 
Previous
 
Next
HomeHomeOur CommunityOur CommunityGeneral Discuss...General Discuss...How can I share the user list with another website, which also uses ASP.Net 2.0 Membership?How can I share the user list with another website, which also uses ASP.Net 2.0 Membership?


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