How to bypass the loggin page (I have good reasons to do so!) [message #4499] |
Sun, 28 July 2002 22:06 |
vidaubannais
Messages: 23 Registered: July 2002
Karma: 0
|
Junior Member |
|
|
Hi guys,
Members already have to loggin in order to be granted access to my site. The point is that now I would like to implement FUD on this existing site, but would like to get rid of it forum's loggin functionality, the reason being that I want to prevent the user to have to loggin twice
As I am not a chanpion in PHP, I don't realy know how to handle the question.
For this reason I was thinking about dumping my already existing users' information database (containing their name, e-mail address, MD5 encripted password etc ... ) right into the FUD FUDXXX_users table to avoid data replication & minimize the modifications in FUD code (if any) - But once this is done and that the information is centralized in FUD table and that this information is accessible by both pattrs (my existing website business logic that I had to modify to fetch data in FUD database, and FUD itself), how could I prevent FUD from prompting for loggin a user that is obviously already logged-in (through my own web site's loggin form)?
Is all of this clear for everyone or shall I repeat for the guys at the last row ?
Thanks in advance!
[Updated on: Sun, 28 July 2002 22:06] Report message to a moderator
|
|
|
|
|
|
Re: How to bypass the loggin page (I have good reasons to do so!) [message #8217 is a reply to message #8202] |
Fri, 17 January 2003 14:19 |
Ilia
Messages: 13241 Registered: January 2002
Karma: 0
|
Senior Member Administrator Core Developer |
|
|
It is possible, I've done it before for commercial clients.
Id is the record id.
user_id is the user id.
ses_id is the session id.
sys_id is an internal data used to auth the URL session.
It may be viable to leave ses_id & sys_id blank, depending on how your system works.
Both, but prefernce is given to cookies.
FUDforum Core Developer
|
|
|