Dockerized IdP

John Gasper jgasper at unicon.net
Tue Mar 8 12:45:50 EST 2016


Scott,

I think you are missing the methodology behind how this container is
intended to be used and honestly how Docker is intended to be used. It's
not like a VM where one goes in and fiddles with files as things need to
be changed. If a change is needed to the IdP config, the old container is
put to bed and a new container based on a new image with the new changes
is brought to life. The base image I provided have the baseline IdP web
app resources. Then a client references my image which overlay their own
changes that would normally go into edit-webapp but lays them onto the
baseline webapp and that because the war-less "war"... They are still
isolated from a config standpoint.

With that said, Jetty does very well just referencing the static web app
files (war-less war). I've had no issues and use it regularly.

-- 
John Gasper
IAM Consultant
Unicon, Inc.
PGP/GPG Key: 0xbafee3ef


>Date: Tue, 8 Mar 2016 15:26:49 +0000
>From: "Cantor, Scott" <cantor.2 at osu.edu>
>To: Shib Users <users at shibboleth.net>
>Subject: RE: Dockerized IdP
>Message-ID:
>	<9846A6064BD102419D06814DD0D78DE11286FE8E at CIO-TNC-D2MBX02.osuad.osu.edu>
>	
>Content-Type: text/plain; charset="us-ascii"
>
>> Jetty has been configured to point directly to the
>> IDP_HOME/webapp directory, so there is no need to run
>> rebuild.sh/rebuild.bat when customizing the idp.war; just overlay your
>> changes.
>
>That strikes me as a bad idea for all sorts of reasons (containers simply
>do not handle that well) and I'm not sure what this buys given that
>overlaying changes would generally require running the build command
>anyway. You should certainly *never* try to redeploy live anyway, which
>eliminates any benefit to this approach.
>
>In fairness, if you're not meant to access the file system of the image,
>then it's mostly academic I suppose
>
>But bottom line is that I would never advise anybody to run with an
>unpacked war in production because all the things you can do to an
>unpacked war are unstable and risky.
>
>-- Scott




More information about the users mailing list