[JIRA] (OSJ-379) "trustAnchors parameter must be non-empty" failure in httpClient

Paul B. Henson (Jira) jira at shibboleth.atlassian.net
Sat May 20 01:44:36 UTC 2023


Paul B. Henson ( https://shibboleth.atlassian.net/secure/ViewProfile.jspa?accountId=5b58f937ffd0a32d7917a0df ) *commented* on OSJ-379 ( https://shibboleth.atlassian.net/browse/OSJ-379?atlOrigin=eyJpIjoiOWM0NzFiYWQyMjViNGU1MDllODQxMjM0MTVlMDg1ZTYiLCJwIjoiaiJ9 )

Re: "trustAnchors parameter must be non-empty" failure in httpClient ( https://shibboleth.atlassian.net/browse/OSJ-379?atlOrigin=eyJpIjoiOWM0NzFiYWQyMjViNGU1MDllODQxMjM0MTVlMDg1ZTYiLCJwIjoiaiJ9 )

I wouldn’t necessarily consider issues resulting from upgrading java and continuing to run the old version a bug. If something was running that had never instantiated a trust store before I’d expect it to fail when it did as the path it would use didn’t exist anymore. What’s weird is that it seems if you already have a valid trust store it will keep working for some indeterminate amount of time then suddenly unexpectedly break 8-/. Assuming that is the underlying root cause it made it kinda hard to correlate <sigh>. I guess I could downgrade/update java on my dev instances a lot and see if it happened more, but I think my best bet is to actually restart jetty when java gets updated and if it never happens again assume that’s what it was.

( https://shibboleth.atlassian.net/browse/OSJ-379#add-comment?atlOrigin=eyJpIjoiOWM0NzFiYWQyMjViNGU1MDllODQxMjM0MTVlMDg1ZTYiLCJwIjoiaiJ9 ) Add Comment ( https://shibboleth.atlassian.net/browse/OSJ-379#add-comment?atlOrigin=eyJpIjoiOWM0NzFiYWQyMjViNGU1MDllODQxMjM0MTVlMDg1ZTYiLCJwIjoiaiJ9 )

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/c52fc610/attachment-0001.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: jira-generated-image-static-comment-icon-3f73c99f-3c97-4b9d-81c4-531ea8571fe3
Type: image/png
Size: 1084 bytes
Desc: not available
URL: <http://shibboleth.net/pipermail/commits/attachments/20230520/c52fc610/attachment-0003.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: jira-generated-image-avatar-5657f651-febc-433c-9e54-a198bb97fcd1
Type: image/png
Size: 345 bytes
Desc: not available
URL: <http://shibboleth.net/pipermail/commits/attachments/20230520/c52fc610/attachment-0004.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: jira-generated-image-static-footer-desktop-logo-85aeafdb-e049-4ee4-bc3e-cb2579895276
Type: image/png
Size: 10805 bytes
Desc: not available
URL: <http://shibboleth.net/pipermail/commits/attachments/20230520/c52fc610/attachment-0005.png>


More information about the commits mailing list