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
Watch
GitHub Core
Show your support for Zikula! Sign up at Github account and watch the Core project!
GitHub Modules
- internetking created topic »password problem« 25. May
- mesteele101 responded to »ERR (3): E_USER_ERROR: Smarty error: [in pagesvar:pagesitem2en line XXX]…« 25. May
- mazdev responded to »Pages 2.5.0 and updating - Page not found« 25. May
- ehdwma created topic »Hide "Register new account" and change template to 3 col« 25. May
- mesteele101 responded to »Zikula 1.3.3 - Selecting a category in Pages not working« 25. May
- mdee created topic »How to implement returnpage ?« 25. May
- nestormateo responded to »Fillters in Clip« 24. May
Zikula Blog
- Anatomy of Open Source Projects on Mar 07
- Continuous Review on Mar 01
- Not Invented Here on Feb 24
- How to Contribute Your Code at Github on Jan 13
- 10 Steps to Coding-Nirvana: Tips for Successful Module Writing on Nov 12
- Submitting Bug Report Tickets That Get Results on Aug 17
- Cozi Tricks #1: Syntax Highlighting on Aug 07
Login
Use different users db table/share login across websites?
-
**unknown user**
- Rank: Freshman
- Registered: Mar 16, 2002
- Last visit: Oct 21, 2009
- Posts: 76
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. -
**unknown user**
- Rank: Registered User
- Registered: Mar 16, 2002
- Last visit: Oct 21, 2009
- Posts: 11
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
- Moderated by:
- Support
