From: "Fraser Campbell" <[EMAIL PROTECTED]>
> On Monday 29 September 2003 15:58, you wrote:
>
> > Like someone else mentioned, use sessions or something like them. The
key
> > is you're passing a unique id around for each person that logs in. When
> > they go to another site, this ID must go with t
Fraser Campbell wrote:
Got it. How about this:
- every login form sets a session ID
- immediately after logging in the user is directed to a page showing that
successful login has occurred. The result screen could could have some
images (or whatever) such as this:
http://www.otherdomain.
On Monday 29 September 2003 15:58, you wrote:
> Like someone else mentioned, use sessions or something like them. The key
> is you're passing a unique id around for each person that logs in. When
> they go to another site, this ID must go with them, so that means they can
> only get to the other s
From: "Fraser Campbell" <[EMAIL PROTECTED]>
> On Monday 29 September 2003 15:33, Kevin Stone wrote:
> >
> > If all domains have access to the same database then there is absolutely
> > nothing preventing you from using a Cookie. Have a normal login on
> > Domain1.com. Once authenticated produce a
On Monday 29 September 2003 15:33, Kevin Stone wrote:
> If all domains have access to the same database then there is absolutely
> nothing preventing you from using a Cookie. Have a normal login on
> Domain1.com. Once authenticated produce a random ID and store it in the
> database. Store the I
Fraser,
Kevin is right on, but it wasn't clear to me that you wanted the users to log onto
each site. Seems you may expect them to go to the site in another browser, or perhaps
the same, without having to signon again. Perhaps this can be done if you do a form
post to the new domain from the
6 matches
Mail list logo
