You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tomcat.apache.org by VAN DER MARLIERE FREDERIC <fr...@cdn.fr> on 2004/12/27 16:03:12 UTC
SSL encryption
Hi all.
I would like to encrypt my login process so that login and password are not
visible on the network. That's why I defined a SSL connector on port 8443 in
my server.xml. My problem is that after the user logged in, request keep on
using the https protocol on port 8443.
Does someone know how to encrypt only the login process and afterwards use
the http protocol again, on port 8080 ?
Thanks.
Fred.
----------------------------------------------------
Ce message et toutes les pieces jointes (ci-apres le "message") sont confidentiels et etablis a l'intention exclusive de ses destinataires.
Toute utilisation ou diffusion non autorisee est interdite.Tout message electronique est susceptible d'alteration.
Le CREDIT DU NORD et ses filiales declinent toute responsabilite au titre de ce message s'il a ete altere, deforme ou falsifie.
This message and any attachments ( the "message") are confidential and intended solely for the addressees.
Any unauthorised use or dissemination is prohibited.E-mails are susceptible to alteration.
Neither CREDIT DU NORD nor any of its subsidiaries or affiliates shall be liable for the message if altered, changed or falsified.
----------------------------------------------------
Re: Multihoming TC
Posted by QM <qm...@brandxdev.net>.
A lot of what you're after is well beyond the scope of current Tomcat
releases, especially the automagic staging/voting/sync/no-restart. (It
sounds as though you want a lot of this to happen within Tomcat, or at
least within the same all-encompassing solution.)
It's certainly *possible*. BEA WebLogic 8.x does this fairly well. If
you want this in Tomcat, it's a matter of writing it, providing patches,
etc.
: I think we understood each other well. We are just looking at the same
: problem from different perspective and with a different scope
Sounds about right. There are some problems I prefer to resolve with a
bit of policy instead of a lot of technology. ;)
-QM
--
software -- http://www.brandxdev.net
tech news -- http://www.RoarNetworX.com
---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-user-help@jakarta.apache.org
Re: Multihoming TC
Posted by John Smith <cm...@acedsl.com>.
on my own previous post.
frontend TC instances don't need to be restarted.
Backend servers could run ant tasks on the front end insts. to reload each
webapp instead of restarting the TC instances
It would also be a nice extra if there is kind of a voting system for
admins to approve updates or disapprove them and discus why with othe admins
in a secure way
----- Original Message -----
From: "John Smith" <cm...@acedsl.com>
To: "Tomcat Users List" <to...@jakarta.apache.org>
Sent: Tuesday, December 28, 2004 10:55 AM
Subject: Re: Multihoming TC
> I am replying to both posters tryin gto consolidate both ideas
>
> > 1/ please post a *new* message when writing to the list.
>
> Sorry, I just got distracted after answering to some people's problems on
> the list.
>
> > 2/ What I've seen a lot of people (myself included) do: develop your app
> > on your test/dev machine; build it into a WAR file; push the WAR out to
> > the production servers at some scheduled time and restart/reload Tomcat.
> Well, that is doable and it is certainly not difficult. Let me recreate it
> the way I am thinking about it:
>
> > 2.1_ develop your app on your test/dev machine
>
> which could be a CVS based one, but I think the synch'ing should be
separate
> from the CVS, dev. . . .
>
> > 2.2_ push the WAR out to the production servers . . .
>
> the 'pushing' part or better said 'synchronization' of all servers should
be
> atomic adn automatic, based on
>
> 2.2.1_ kind of a synchronization protocoll,
>
> 2.2.2_ that knows of the location of the other machines and that they all
> were time synch'ed
>
> 2.2.3_ their latest tree-like 'signature' structure for the data in:
>
> 2.2.3.1_ databases; down to a record level ('creation' and 'last updated'
> time stamps must be kept for each record which is always good anyway when
> you need (an you always do) optimistic locking, concurrent updates, etc)
and
> ('mirror/rsync' works for file systems only, right?) Separating DB updates
> from webapp ones is also good because in DB-driven sites must updates are
> made to the data . . .
>
> 2.2.3.2_ and the code; down to the classes' MD5 signatures (JARs are way
to
> grob for this, usually you just change a class, or a web.xml file not the
> whole webapp)
>
> > at some scheduled time
>
> I don't quite like the idea of a 'scheduled time', I would rather go with
> pushed 'landmark' updates, or maybe giving both as options. Also
automation
> is always good for DOS attacks, I think updating a live site needs some
hot
> blood and bony skulls backing/being aware of it
>
> 2.2.4 > restart/reload Tomcat
>
> I don't like the idea of having to restart TC in a production server, at
> least not as part of the replication strat.
>
> I would rather go with a backend "staging server" that would keep a copy
of
> the lastest sync'ed 'site images'. This is were all updates are made prior
> to 'restarting TC' and this backend "staging server" is also the one
> brokering all:
>
> 2.2.4.1_ HTTP 404-like errors
>
> 2.2.4.2_ and exceptions
>
> with customized redirections, searches, etc. There could also be 'master'
> stage servers (just in case that many people work concurrently) and
> slave/replicated ones
>
> This backend server would be also connected to the same DB that front
ends
> connect too
>
> 2.3._ Once these tree-like 'signatures' of all back end servers is the
same,
> so we know that all copies of the data and code ar OK, the front end
servers
> would be updated by either:
>
> 2.3.1_ 'restarting' the front instances (that would get their data feeds
> from the same backend directory structure) or
>
> 2.3.2_ CD-ROMs could be burned
>
> 2.3.3_ classes could be read/loaded from a DB . . .
>
> I think this is good also because even if the updates are automatic the
> 'commited' ones are not and things can be still changed/fine tune prior to
> commiting an update. Basically 'deltas' will be visible to all mirror
sites'
> admins that can check them and decide what should be commited or not . . .
>
> > The push is OS-specific; in Unix-style environments, I've used
everything
> from a scripted scp or rsync to a manual FTP.
> I was kind of thinking about making it happen as part of a synch'ing
> protocoll that does not need extra port or nothing it would be a HTTP/SSL
> (partially of totally) communication with data transfers and all between
all
> backend staging servers
>
> > Does this answer your question, or did I misunderstand it?
>
> I think we understood each other well. We are just looking at the same
> problem from different perspective and with a different scope
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: tomcat-user-help@jakarta.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-user-help@jakarta.apache.org
Re: Multihoming TC
Posted by John Smith <cm...@acedsl.com>.
I am replying to both posters tryin gto consolidate both ideas
> 1/ please post a *new* message when writing to the list.
Sorry, I just got distracted after answering to some people's problems on
the list.
> 2/ What I've seen a lot of people (myself included) do: develop your app
> on your test/dev machine; build it into a WAR file; push the WAR out to
> the production servers at some scheduled time and restart/reload Tomcat.
Well, that is doable and it is certainly not difficult. Let me recreate it
the way I am thinking about it:
> 2.1_ develop your app on your test/dev machine
which could be a CVS based one, but I think the synch'ing should be separate
from the CVS, dev. . . .
> 2.2_ push the WAR out to the production servers . . .
the 'pushing' part or better said 'synchronization' of all servers should be
atomic adn automatic, based on
2.2.1_ kind of a synchronization protocoll,
2.2.2_ that knows of the location of the other machines and that they all
were time synch'ed
2.2.3_ their latest tree-like 'signature' structure for the data in:
2.2.3.1_ databases; down to a record level ('creation' and 'last updated'
time stamps must be kept for each record which is always good anyway when
you need (an you always do) optimistic locking, concurrent updates, etc) and
('mirror/rsync' works for file systems only, right?) Separating DB updates
from webapp ones is also good because in DB-driven sites must updates are
made to the data . . .
2.2.3.2_ and the code; down to the classes' MD5 signatures (JARs are way to
grob for this, usually you just change a class, or a web.xml file not the
whole webapp)
> at some scheduled time
I don't quite like the idea of a 'scheduled time', I would rather go with
pushed 'landmark' updates, or maybe giving both as options. Also automation
is always good for DOS attacks, I think updating a live site needs some hot
blood and bony skulls backing/being aware of it
2.2.4 > restart/reload Tomcat
I don't like the idea of having to restart TC in a production server, at
least not as part of the replication strat.
I would rather go with a backend "staging server" that would keep a copy of
the lastest sync'ed 'site images'. This is were all updates are made prior
to 'restarting TC' and this backend "staging server" is also the one
brokering all:
2.2.4.1_ HTTP 404-like errors
2.2.4.2_ and exceptions
with customized redirections, searches, etc. There could also be 'master'
stage servers (just in case that many people work concurrently) and
slave/replicated ones
This backend server would be also connected to the same DB that front ends
connect too
2.3._ Once these tree-like 'signatures' of all back end servers is the same,
so we know that all copies of the data and code ar OK, the front end servers
would be updated by either:
2.3.1_ 'restarting' the front instances (that would get their data feeds
from the same backend directory structure) or
2.3.2_ CD-ROMs could be burned
2.3.3_ classes could be read/loaded from a DB . . .
I think this is good also because even if the updates are automatic the
'commited' ones are not and things can be still changed/fine tune prior to
commiting an update. Basically 'deltas' will be visible to all mirror sites'
admins that can check them and decide what should be commited or not . . .
> The push is OS-specific; in Unix-style environments, I've used everything
from a scripted scp or rsync to a manual FTP.
I was kind of thinking about making it happen as part of a synch'ing
protocoll that does not need extra port or nothing it would be a HTTP/SSL
(partially of totally) communication with data transfers and all between all
backend staging servers
> Does this answer your question, or did I misunderstand it?
I think we understood each other well. We are just looking at the same
problem from different perspective and with a different scope
---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-user-help@jakarta.apache.org
Re: Multihoming TC
Posted by Tim Funk <fu...@joedog.org>.
There are a few ways.
1) Make sure all your changes are in CVS. Then have your servers build the
webapp from CVS. You'll need a script to detect when a new release is
available - this should be easy to accomplish.
2) Use mirror/rsync to publish all the files to each server. I suggest not
publishing directly to the webapp area itself - but to another location on
the server. Then the server can run a local sync. Why? If you need to publish
to 2 servers - and the first publish fails half way - your servers can get
out of sync.
cron and simple wrapper scripts are your friend
-Tim
John Smith wrote:
> Say you have a number of TC instances running from different boxes/IP
> addresses/locations, and you develop from one of the boxes.
>
> How do you replicate all data/code in all other instances in a reliable way
> are there RFC or a standard replication protocol to do that?
>
> I have read a number of posts complaining about TC's implementations of
> webdav and do know there are 'ways' (including the always inviting 'monkey'
> ones) to do that, but I am asking about best practices that work well with
> TC.
>
> How do people make these kinds of things happen?
>
---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-user-help@jakarta.apache.org
Re: Multihoming TC
Posted by QM <qm...@brandxdev.net>.
On Tue, Dec 28, 2004 at 06:08:06AM -0500, John Smith wrote:
: Say you have a number of TC instances running from different boxes/IP
: addresses/locations, and you develop from one of the boxes.
:
: How do you replicate all data/code in all other instances in a reliable way
: are there RFC or a standard replication protocol to do that?
1/ please post a *new* message when writing to the list. Replying to
an old (unrelated) message confuses thread-aware mailers, which makes
your question harder to find (and thus answer).
2/ What I've seen a lot of people (myself included) do: develop your app
on your test/dev machine; build it into a WAR file; push the WAR out to
the production servers at some scheduled time and restart/reload Tomcat.
The push is OS-specific; in Unix-style environments, I've used
everything from a scripted scp or rsync to a manual FTP.
Does this answer your question, or did I misunderstand it?
-QM
--
software -- http://www.brandxdev.net
tech news -- http://www.RoarNetworX.com
---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-user-help@jakarta.apache.org
Multihoming TC
Posted by John Smith <cm...@acedsl.com>.
Say you have a number of TC instances running from different boxes/IP
addresses/locations, and you develop from one of the boxes.
How do you replicate all data/code in all other instances in a reliable way
are there RFC or a standard replication protocol to do that?
I have read a number of posts complaining about TC's implementations of
webdav and do know there are 'ways' (including the always inviting 'monkey'
ones) to do that, but I am asking about best practices that work well with
TC.
How do people make these kinds of things happen?
---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-user-help@jakarta.apache.org
Re: SSL encryption
Posted by John Smith <cm...@acedsl.com>.
I think you may do that the same way that hotmail and google does, namely;
immediatly redirecting the user after loggin and placing some user
authorized/online flag on a database
run ethereal and trace the request/responce conversation while logging into
hotmail . . .
----- Original Message -----
From: "VAN DER MARLIERE FREDERIC" <fr...@cdn.fr>
To: <to...@jakarta.apache.org>
Sent: Monday, December 27, 2004 10:03 AM
Subject: SSL encryption
> Hi all.
>
> I would like to encrypt my login process so that login and password are
not
> visible on the network. That's why I defined a SSL connector on port 8443
in
> my server.xml. My problem is that after the user logged in, request keep
on
> using the https protocol on port 8443.
>
> Does someone know how to encrypt only the login process and afterwards use
> the http protocol again, on port 8080 ?
>
> Thanks.
> Fred.
>
>
> ----------------------------------------------------
> Ce message et toutes les pieces jointes (ci-apres le "message") sont
confidentiels et etablis a l'intention exclusive de ses destinataires.
> Toute utilisation ou diffusion non autorisee est interdite.Tout message
electronique est susceptible d'alteration.
> Le CREDIT DU NORD et ses filiales declinent toute responsabilite au titre
de ce message s'il a ete altere, deforme ou falsifie.
> This message and any attachments ( the "message") are confidential and
intended solely for the addressees.
> Any unauthorised use or dissemination is prohibited.E-mails are
susceptible to alteration.
> Neither CREDIT DU NORD nor any of its subsidiaries or affiliates shall be
liable for the message if altered, changed or falsified.
> ----------------------------------------------------
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-user-help@jakarta.apache.org
SV: SSL encryption
Posted by Roland Carlsson <ro...@alfa-moving.se>.
Hi!
SSL in tomcat does not allow for having the same session both http and
https. Something about developer misstakes leading to security-holes that
would reflekt badly back on Tomcat... At least that is the answer I got.
You can write your own Connector if you really need to work your way around
this.
Regards
Roland Carlsson
Den 04-12-27 16.03, skrev "VAN DER MARLIERE FREDERIC"
<fr...@cdn.fr>:
> Hi all.
>
> I would like to encrypt my login process so that login and password are not
> visible on the network. That's why I defined a SSL connector on port 8443 in
> my server.xml. My problem is that after the user logged in, request keep on
> using the https protocol on port 8443.
>
> Does someone know how to encrypt only the login process and afterwards use
> the http protocol again, on port 8080 ?
>
> Thanks.
> Fred.
>
>
> ----------------------------------------------------
> Ce message et toutes les pieces jointes (ci-apres le "message") sont
> confidentiels et etablis a l'intention exclusive de ses destinataires.
> Toute utilisation ou diffusion non autorisee est interdite.Tout message
> electronique est susceptible d'alteration.
> Le CREDIT DU NORD et ses filiales declinent toute responsabilite au titre de
> ce message s'il a ete altere, deforme ou falsifie.
> This message and any attachments ( the "message") are confidential and
> intended solely for the addressees.
> Any unauthorised use or dissemination is prohibited.E-mails are susceptible to
> alteration.
> Neither CREDIT DU NORD nor any of its subsidiaries or affiliates shall be
> liable for the message if altered, changed or falsified.
> ----------------------------------------------------
>
---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-user-help@jakarta.apache.org