Dockerized IdP

[Etienne Dysli-Metref]

On 07/03/16 22:40, John Gasper wrote:
> I wanted to take a moment and share a project that I've been working on
> for the last year. That project is a dockerized Shibboleth IdP image,
> which includes Java and Jetty. With this image, one simply overlays
> their local configuration changes, builds the custom image, and they are
> up in seconds. If someone needs a new configuration, it supports easily
> provisioning (and externalizing) a new IdP configuration.

Thanks for sharing John!
One question that always puzzled me with Docker is: how do you properly
manage the application's configuration? Your example shows several
possibles answers. :)

I think externalising the whole configuration is best, because then you
would only have one image to build and you could run it several times
with different configurations. (Assuming a context where one would run
many IdPs, one per customer.)

How many IdP (same or different config) do you plan to run with Docker?
on how many hosts?

> I think this is the answer if you are thinking of running the IdP in
> Docker, but feel free to make up your own mind.

What does thing bring compared to managing IdPs with configuration
management software? I mean you'd need CM anyway to create the IdP's
configuration (whether in the image or external), so why bother with
Docker on top of this?

Cheers,
   Etienne

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: OpenPGP digital signature
URL: <http://shibboleth.net/pipermail/users/attachments/20160308/249570c1/attachment.sig>