[JIRA] (IDP-1961) Allow custom HttpClient for IdP update (e.g. HTTP Proxy)

Rod Widdowson (Jira) jira at shibboleth.atlassian.net
Sat May 20 15:43:33 UTC 2023


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

Re: Allow custom HttpClient for IdP update (e.g. HTTP Proxy) ( https://shibboleth.atlassian.net/browse/IDP-1961?atlOrigin=eyJpIjoiMjU3ZjBhNDEwNGFkNDBjZGI2NmZhNmFjMGUxY2Y3NDciLCJwIjoiaiJ9 )

There is a pretty hideous catch-22 going on in here and I am not sure how to square it.

The install program now only exists (and only has any meaning) within the auspices of the distribution tree. This means that such as it is, idp.home is the DISTRIBUTION. OF course there is not idp.properties and so we find nothing and so all the magical wiring inside the command line stuff won’t work.

Of course I am borrowing - home as an easy way find the distribution. But I don’t see that telling people to specify -home to point to the “to be upgraded” directory is a good idea. I’ll poke at the classes, I am wondering whether it’s possible to force the internals to think that the idphome is the target (specified with -'t).

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

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#100225- sha1:9dd72a2 )
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://shibboleth.net/pipermail/commits/attachments/20230520/bbe36ff4/attachment-0001.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: jira-generated-image-avatar-243e8cbe-cc12-4232-b938-182ab6b078d0
Type: image/png
Size: 457 bytes
Desc: not available
URL: <http://shibboleth.net/pipermail/commits/attachments/20230520/bbe36ff4/attachment-0003.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: jira-generated-image-static-comment-icon-6cbeabdd-a853-4d8a-9f51-86a9b0b2d7d9
Type: image/png
Size: 1084 bytes
Desc: not available
URL: <http://shibboleth.net/pipermail/commits/attachments/20230520/bbe36ff4/attachment-0004.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: jira-generated-image-static-footer-desktop-logo-9ad8f034-ac68-449c-96f2-05e031ea4719
Type: image/png
Size: 10805 bytes
Desc: not available
URL: <http://shibboleth.net/pipermail/commits/attachments/20230520/bbe36ff4/attachment-0005.png>


More information about the commits mailing list