<html><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /></head><body style='font-size: 10pt; font-family: Verdana,Geneva,sans-serif'>
<p>Hello all!</p>
<p>We have installed Shibboleth SP 3.3.0 in AlmaLinux 9 (RPM Install - we used the repository file of RHEL 8, as for RHEL 9 there is not a repository file). In shibboleth2.xml when we add a Metadata Provider of remotely supplied batch of signed metadata as below:</p>
<p><MetadataProvider type="XML" validate="false" url="https://idp.example.com/metadata.xml" backingFilePath="metadata.xml" maxRefreshDelay="7200"><br /></MetadataProvider></p>
<p>we get the following error:</p>
<p><span># systemctl restart shibd</span><br /><em>Job for shibd.service failed because a fatal signal was delivered causing the control process to dump core.</em><br /><em>See "systemctl status shibd.service" and "journalctl -xeu shibd.service" for details.</em></p>
<p><span># shibd -t<br /><em>2022-09-16 09:33:32 WARN Shibboleth.DEPRECATION : MetadataGenerator handler</em><br /><em>Segmentation fault (core dumped)</em></span></p>
<p><span># systemctl status shibd</span></p>
<p><em>● shibd.service - Shibboleth Service Provider Daemon</em></p>
<p><em>Loaded: loaded (... enabled; vendor preset: disabled)</em></p>
<p><em>Active: activating (auto-restart) (Result: core-dump) since ...</em></p>
<p><em>Process: 51868 ExecStart=/usr/sbin/shibd -f -F (code=dumped, signal=SEGV)<br /> Main PID: 51868 (code=dumped, signal=SEGV)<br /> CPU: 83ms</em></p>
<p>If we add instead a Metadata Provider of locally maintained metadata as below:</p>
<p><em><MetadataProvider type="XML" validate="false" path="/var/cache/shibboleth/metadata.xml"></em><br /><em></MetadataProvider></em></p>
<p>we do't get errors.</p>
<p>Any ideas on the above issue are welcomed.</p>
<p>Thank you in advance,</p>
<p>Vasilis Bekos</p>
</body></html>