[JIRA] (IDP-2136) Consider Splitting the Windows Installer into IdP and Jetty+Procrun
Rod Widdowson (Jira)
jira at shibboleth.atlassian.net
Sat Jul 1 14:39:34 UTC 2023
Rod Widdowson ( https://shibboleth.atlassian.net/secure/ViewProfile.jspa?accountId=59fb32bbc24efb3c4ed3c977 ) *commented* on IDP-2136 ( https://shibboleth.atlassian.net/browse/IDP-2136?atlOrigin=eyJpIjoiZWE0NzNiOWQ5YWMwNDc5NGEwMTM1YTE2YmZhNWQ2MmIiLCJwIjoiaiJ9 )
Re: Consider Splitting the Windows Installer into IdP and Jetty+Procrun ( https://shibboleth.atlassian.net/browse/IDP-2136?atlOrigin=eyJpIjoiZWE0NzNiOWQ5YWMwNDc5NGEwMTM1YTE2YmZhNWQ2MmIiLCJwIjoiaiJ9 )
So The basic idea here is to remove pretty much everything from the current install except parameter capture (from history by way of the regstry if needed ). The IdP install then
* Unpacks the distribution into c:\ProgramData\Shibboleth\IdP\Dist
* Writes the property file to drive the installer
* And runs the installer
Note that it does NOT
* Muck around with jetty, jetty-base or procrun (beyond uninstalling the current ones)
* Put anything directly into idp.home itself (only indirectly via the standard install).
This is important since it allows the user to update the IdP in the canonical way (unzip the ditro and run “install”)
The Jetty bit
* Fails if there isn’t a current V5 IdP
* Captures “Some parameters” from the registry
* IdP Home
* ???
* Captures “Some” more parameters from history by way of the registry
* JETTYD_USER and JETTYD_DOMAIN
* Slams procrun, Jetty and Jetty-base directly into the correct locations (the first two as a peer of idp.home, the last as a child)
* Just like now
* Does the same install as now
* Details TBD - but I have a horrid fear that the quickest way to get this will be via ant
* Does the reprotect of the critical folders (in both the IdP and Jetty). Since all folders are created (and never deleted) by the Java bit of the IdP installer the ACLS can be assumed to be sticky.
( https://shibboleth.atlassian.net/browse/IDP-2136#add-comment?atlOrigin=eyJpIjoiZWE0NzNiOWQ5YWMwNDc5NGEwMTM1YTE2YmZhNWQ2MmIiLCJwIjoiaiJ9 ) Add Comment ( https://shibboleth.atlassian.net/browse/IDP-2136#add-comment?atlOrigin=eyJpIjoiZWE0NzNiOWQ5YWMwNDc5NGEwMTM1YTE2YmZhNWQ2MmIiLCJwIjoiaiJ9 )
Get Jira notifications on your phone! Download the Jira Cloud app for Android ( https://play.google.com/store/apps/details?id=com.atlassian.android.jira.core&referrer=utm_source%3DNotificationLink%26utm_medium%3DEmail ) or iOS ( https://itunes.apple.com/app/apple-store/id1006972087?pt=696495&ct=EmailNotificationLink&mt=8 ) This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100227- sha1:9e449c4 )
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://shibboleth.net/pipermail/commits/attachments/20230701/a445a2d7/attachment-0001.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: jira-generated-image-avatar-c715fb5b-138c-4eca-be8c-b05f2e2db7fa
Type: image/png
Size: 457 bytes
Desc: not available
URL: <http://shibboleth.net/pipermail/commits/attachments/20230701/a445a2d7/attachment-0003.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: jira-generated-image-static-comment-icon-0eeaec0d-caec-4c54-ad2c-0df2e6ef01a7
Type: image/png
Size: 1084 bytes
Desc: not available
URL: <http://shibboleth.net/pipermail/commits/attachments/20230701/a445a2d7/attachment-0004.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: jira-generated-image-static-footer-desktop-logo-a9fc04be-a0f7-4d27-a3da-c4678264ac9d
Type: image/png
Size: 10805 bytes
Desc: not available
URL: <http://shibboleth.net/pipermail/commits/attachments/20230701/a445a2d7/attachment-0005.png>
More information about the commits
mailing list