| Message Text |
I have a somewhat unique member integration issue. My current member and group tables exist in a MS SQL Server database. My site uses ASP for authentication processing.
My plan is to add some code to my current registration process that will insert a new row into the WSN Links member table in
the MySQL database when a new member confirms their registration. I will of course import all of my existing members into the WSN Links member table as well.
I will be modifying the necessary WSN Links pages so that members will always login using the current process. That is, they will never login using the WSN Links process.
But first I have a few questions:
1. What fields are required in the WSN Links member table? Obviously I'll need to insert the id, name, password, email, validated, and usergroup fields. Are there any others? I realize that I will need to turn off the auto_increment function on the id field.
2. Regarding groups, my current system uses 3 tables to assign members to groups (members can be assigned to more than one group) whereas it appears that WSN Links uses just 2. I'm not sure this will be too much of an issue because I mainly just need to track "all members" and "administrators" for my links, and I'm the only administrator anyway. But if I do need to track additional groups, how should those be inserted into the secondarygroups field (numbers separated by commas or something)?
3. If I set the wsnuser and wsnpassword cookies as part of my current login process, is that all I need to do so that members will be logged in to WSN Links?
I think that's it for now. Thanks. |
