[JIRA] (IDP-1961) Allow custom HttpClient for IdP update (e.g. HTTP Proxy)
2df9c075-b75b-4dad-a483-2c4ba2d6147e@https://weblogin.uni-marburg.de/idp/shibboleth (Jira)
jira at shibboleth.atlassian.net
Mon Jun 13 07:49:43 UTC 2022
2df9c075-b75b-4dad-a483-2c4ba2d6147e at https://weblogin.uni-marburg.de/idp/shibboleth ( https://shibboleth.atlassian.net/secure/ViewProfile.jspa?accountId=60e5bc20f90dee0069525ec7 ) *commented* on IDP-1961 ( https://shibboleth.atlassian.net/browse/IDP-1961?atlOrigin=eyJpIjoiNTVhZTExZjkwZjYzNDBiN2I4YjIwYjc4NThjNWU0MmQiLCJwIjoiaiJ9 )
Re: Allow custom HttpClient for IdP update (e.g. HTTP Proxy) ( https://shibboleth.atlassian.net/browse/IDP-1961?atlOrigin=eyJpIjoiNTVhZTExZjkwZjYzNDBiN2I4YjIwYjc4NThjNWU0MmQiLCJwIjoiaiJ9 )
Well, I guess that I had expected some update magic here, as the installer automatically tried to upgrade the OIDC plugins along with the IdP update process.
If there was a way to use the plugin installer parameters (suitable for ./bin/plugin.sh) with the IdP installer (./bin/install.sh), I would be able to use the common update path. Otherwise I am left with a “broken” installer if I have plugins installed which are required to be updated along with the IdP update.
Our security guidelines urge me to run only a loadbalancer on a public IP address, while running the servlet container (Tomcat 9) on an isolated server with an internal IP address. There is no NAT, but only a http(s) proxy. So having a way to perform an IdP upgrade using either the HTTP proxy or offline files (including the plugin upgrades within the IdP upgrade process) would be a nice thing.
( https://shibboleth.atlassian.net/browse/IDP-1961#add-comment?atlOrigin=eyJpIjoiNTVhZTExZjkwZjYzNDBiN2I4YjIwYjc4NThjNWU0MmQiLCJwIjoiaiJ9 ) Add Comment ( https://shibboleth.atlassian.net/browse/IDP-1961#add-comment?atlOrigin=eyJpIjoiNTVhZTExZjkwZjYzNDBiN2I4YjIwYjc4NThjNWU0MmQiLCJwIjoiaiJ9 )
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#100200- sha1:9199305 )
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://shibboleth.net/pipermail/commits/attachments/20220613/7b81af6c/attachment-0001.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: jira-generated-image-static-comment-icon-fec6420c-cc36-41a3-a245-0819b2548ea5
Type: image/png
Size: 1084 bytes
Desc: not available
URL: <http://shibboleth.net/pipermail/commits/attachments/20220613/7b81af6c/attachment-0003.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: jira-generated-image-avatar-d0951f2a-5fa9-407a-a9ef-411af2304ab8
Type: image/png
Size: 457 bytes
Desc: not available
URL: <http://shibboleth.net/pipermail/commits/attachments/20220613/7b81af6c/attachment-0004.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: jira-generated-image-static-footer-desktop-logo-a33b1d2a-d602-4222-a02d-1ae2a241b992
Type: image/png
Size: 10805 bytes
Desc: not available
URL: <http://shibboleth.net/pipermail/commits/attachments/20220613/7b81af6c/attachment-0005.png>
More information about the commits
mailing list