Yet another sessions/authentication question

Do you have a question? Post it now! No Registration Necessary.  Now with pictures!

Threaded View
The following is entirely hypothetical.
I have been thinking about venturing into this, but I have not yet done so:

Let's say I have a dedicated server somewhere. I control it.
I also have a specialized clientèle: retail store owners
who want shopping carts.  But each such site also want
to build a social networking marketing scheme.
So they want:

richly informational sites with many "display" pages.
1) An interactive bulletin board forum (I want to use phorum)
2) A blogging system so returning customers can blather (I want to use

3) A shopping cart system with a rich backend customer relations shema
    (I want to run Tomcat as well as Apache, so I can use OSCommerce)

At this point I'm trying to build a corral around three separate systems
(forum, blogging and shopping cart) that each require and use their
own custom login procedure.  But I don't want to force incoming users
to be logging in to separate mechanisms three different times.

I guess there is no answer, not without hacking the code for each
such system. Is there some sort of an uber-authentication mechanism
separate software systems (like the above) could be hacked use?

OSCommerce is the dangerous part. I suppose I could look at their
login stuff, and then try to hack Wordpress and Phorum to use it too.

I just wondered what most developers do. This seems like it must
be a recurring problem.

Re: Yet another sessions/authentication question

salmobytes schreef:
Quoted text here. Click to load it


For what it is worth: I hacked a single sign-on into WikiMedia (the
wikipedia software).
People had to log on either in the wiki or in my own webapplication.
In this case it was relatively easy because wikimedia offers a
contraption named 'hooks' to execute custom PHP code on certain events.

I don't think you will find a piece of software that can manage this for
you with arbitary other packages. It is just handwork.

just my 2 cent.

Erwin Moller

"There are two ways of constructing a software design: One way is to
make it so simple that there are obviously no deficiencies, and the
other way is to make it so complicated that there are no obvious
deficiencies. The first method is far more difficult."
-- C.A.R. Hoare

Site Timeline