Hi Peter,
On 1/25/07, Peter Stavrinides <[EMAIL PROTECTED]> wrote:
Greg thanks for this, sounds like it has potential, and It wont be a
problem with separate machines, but one problem I foresee though is the
new IE7 browser which disables cookies on the client by default, have
you tested it?
Greg thanks for this, sounds like it has potential, and It wont be a
problem with separate machines, but one problem I foresee though is the
new IE7 browser which disables cookies on the client by default, have
you tested it?
Christopher, I am currently using the Authorization header but the
Christopher Schultz wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Peter,
Peter Stavrinides wrote:
I do mention however that two separate physical servers exist and the
webapps are on two separate web servers as well... they appear under the
same host to users because the URL's are dynam
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Peter,
Peter Stavrinides wrote:
> I do mention however that two separate physical servers exist and the
> webapps are on two separate web servers as well... they appear under the
> same host to users because the URL's are dynamically rewritten on the
Peter,
I think this can be done with mod_auth_cookie_myql.
You will, however, have to write your own little SSO-Servlet / JSP
which updates the MySQL-DB with the JSSOSessionID-Cookie provided by
Tomcat. Apache will then read the Cookie from the database, check, if
this cookie is present on the c
Christopher, thanks for your reply.
I do mention however that two separate physical servers exist and the
webapps are on two separate web servers as well... they appear under the
same host to users because the URL's are dynamically rewritten on the
front end. The DNS is entirely separate, so t
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Peter,
Peter Stavrinides wrote:
> I have an Apache web server with Basic authentication configured to use
> a Postgres database. Web application A (written in Perl) uses it.
>
> Web application B (written in Java) runs on Tomcat 5.5.20 on a different
