<html><head><meta http-equiv="Content-Type" content="text/html; charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><div><blockquote type="cite" class=""><div class="">On 15 Jun 2019, at 22:32, Philip Prindeville <<a href="mailto:philip.prindeville@gigamon.com" class="">philip.prindeville@gigamon.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><span style="caret-color: rgb(0, 0, 0); font-family: Menlo-Regular; font-size: 13px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none; float: none; display: inline !important;" class="">My understanding of Shibboleth is that it gets configured, then installed, then built/rebuilt in the target directory, which is almost the reverse of the traditional RPM packaging steps.</span></div></blockquote></div><br class=""><div class="">I think that's a fair summary, as far as it goes. It's like that for good reasons, of course: the mechanism by which IdP extensions and customisations are incorporated into what the servlet container sees being the most obvious.</div><div class=""><br class=""></div><div class="">The other aspect you haven't touched on is the dependency on the servlet container, and the way in which the two are integrated. Both RHEL/CentOS 6 and 7 come with versions of Tomcat and Jetty we don't support and wouldn't actually recommend, so you might end up needing to repackage newer versions (along with the integration configuration, which isn't part of the IdP product) as well as the IdP.</div><div class=""><br class=""></div><div class="">Not saying this is impossible, by any means, but it's far from easy which is I guess why someone hasn't done it already. I'd be particularly wary of putting a lot of effort into packaging for CentOS 6, which only has 18 months or so left to run. I'd be pretty surprised if anyone was making new deployments based on it, given that RHEL 8 is already out (and CentOS 8 soon(TM)).</div><div class=""><br class="webkit-block-placeholder"></div><div class="">It's definitely going to depend on _why_ you want to do this, which you haven't indicated in your post. If what you're trying to do is build a packaging solution for the future, for a large number of systems, I'd suggest looking at (Linux) containers instead. Several people have built IdP appliances using Docker-like systems, and although it's still tricky depending on what level of customisation you want there's at least proof of concept level stuff out there.</div><div class="">
<span class="Apple-style-span" style="border-collapse: separate; color: rgb(0, 0, 0); font-family: Helvetica; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; border-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-stroke-width: 0px;"><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><span class="Apple-style-span" style="border-collapse: separate; color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; border-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-stroke-width: 0px;"><div class=""><span class="Apple-tab-span" style="white-space: pre;"><br class="Apple-interchange-newline"></span> -- Ian<br class=""></div><div class=""><span class="Apple-style-span" style="font-size: medium;"><br class=""></span></div></span></div></span><br class="Apple-interchange-newline"><br class="Apple-interchange-newline">
</div>
<br class=""></body></html>