[JIRA] (IDP-1927) Make Jetty run under its own credentials for windows installs

[Rod Widdowson (Jira)]

Rod Widdowson ( https://shibboleth.atlassian.net/secure/ViewProfile.jspa?accountId=59fb32bbc24efb3c4ed3c977 ) *commented* on IDP-1927 ( https://shibboleth.atlassian.net/browse/IDP-1927?atlOrigin=eyJpIjoiMjUyN2VlYzIxNTU0NDMzZWI3NTQ1OWE2YjJkZWFjZWIiLCJwIjoiaiJ9 )

Re: Make Jetty run under its own credentials for windows installs ( https://shibboleth.atlassian.net/browse/IDP-1927?atlOrigin=eyJpIjoiMjUyN2VlYzIxNTU0NDMzZWI3NTQ1OWE2YjJkZWFjZWIiLCJwIjoiaiJ9 )

There is an interesting problem here.

We can, within one component

* install procrun
* create the user
* create the service

My concern is to what happens if procrun gets updated. I suspect that at that point the component may be uninstalled and re-installed.

I think I can persuade the user (and hence its SSID) to stay around (at the cost of it being there after a final install), my problem is that the password will need to be regenerated (the only alternative being that we save the password somewhere and I ain't doing that).

This in turn means that we have to either

* trust the password generation (its a GUID and so unique but possibly predictable)
* Or tell the installer to always update the password after an update (or to specify a password which works for them on the command line)

Just capturing this for now.

( https://shibboleth.atlassian.net/browse/IDP-1927#add-comment?atlOrigin=eyJpIjoiMjUyN2VlYzIxNTU0NDMzZWI3NTQ1OWE2YjJkZWFjZWIiLCJwIjoiaiJ9 ) Add Comment ( https://shibboleth.atlassian.net/browse/IDP-1927#add-comment?atlOrigin=eyJpIjoiMjUyN2VlYzIxNTU0NDMzZWI3NTQ1OWE2YjJkZWFjZWIiLCJwIjoiaiJ9 )

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#100207- sha1:bddf6e1 )
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://shibboleth.net/pipermail/commits/attachments/20221004/e189a6cd/attachment-0001.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: jira-generated-image-static-comment-icon-cbc8f20e-d50c-4920-ad89-1f6866b0b947
Type: image/png
Size: 1084 bytes
Desc: not available
URL: <http://shibboleth.net/pipermail/commits/attachments/20221004/e189a6cd/attachment-0003.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: jira-generated-image-avatar-caf45966-aa6d-4487-9838-d8c0d9a43967
Type: image/png
Size: 457 bytes
Desc: not available
URL: <http://shibboleth.net/pipermail/commits/attachments/20221004/e189a6cd/attachment-0004.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: jira-generated-image-static-footer-desktop-logo-358df1c6-b24d-4c4f-a831-34a7981a3cab
Type: image/png
Size: 10805 bytes
Desc: not available
URL: <http://shibboleth.net/pipermail/commits/attachments/20221004/e189a6cd/attachment-0005.png>