Dizkus

Hi community

I have a central database with a lot of information on a large number of people. I have different websites (based on PN 7.6.2) where I would like these people to have access, and it would really be convenient to have their login/user-information stored centrally in this database. There's also a lot of information in the database that doesn't fit in a pn_users table. I need a lot of modules which is integrated with the users module (like pnForum) so I can't just write a login/authentication procedure for the current database - I has to be linked with users module in one way or another.

Does anyone have any experience in changing the whole register/authentication part of PN? I could imagine that it could be quite challenging on 7.6.2 because of the way the users module is done. Any changes on this in 0.8? (not that I can wait for it to become stable - just being curios:) )
Another approach is keeping the current database and pn_users seperate and having some external script syncronize user information, but I'm not sure how this should work as changes could be done in both tables. Am I really forced to store login-information for each website seperately or is their any workaround?

Any suggestions? - I can't be the only one who can't do with a simple pn_users table in all situations?

Thank you very much in advance!

Best regards, Jonas Delfs

I am VERY intersted in this as well .I have a nice auction PHP script I would like to share the PostNuke users. Any help here is nice.

what i have done on my site is to change several (will have to look up which exactly) table from pn_ to shared_ to show for my self i shared them. then i changed the pntables.php in the root directory ( and 1 or 2 modules pntables.php's) and also setup a
joined login between my 3 sites. I always wanted to wite a howto/whitebook but never got round to it. Perhaps i should.

A How to on this login hack would be great. IF you have the time.

Ill see if i can whip something up over the weekend. might be a bit longer as my trusted ibook has decided to die on me.

i know i have been bad, but ill really do it this weekend

If you've got access to Mysql >= 5.0.1 the neat solution would be dropping pn_users and setting up a view based on the central users database ('myusers'), if I'm not mistaken. Unfortuneately the project I'm doing at the moment currently has to run on 4.1.

I hate hacking, so only touching the database would be optimal...

For another project I've set up a cron job to throw login-information into pn_users from 'myusers' regularly, and made sure that modifications are only made in the 'myusers' table. This only required little hacking, but still isn't half as pretty as the views-solution.

Just some thoughts that somebody might be able to use... feel free!:)

Regards, Jonas



edited by: jonasdelfs, Aug 18, 2006 - 03:28 PM