"no signing credential resolved, leaving message unsigned"

[sacha+shibboleth at ssl.co.uk]

On 18/06/2025 20:25, Cantor, Scott wrote:
>> Turned out the permissions on the signing & encryption keys were
>> such that shibd couldn't read them. Not sure why it wasn't
>> screaming about it into the logs, or why shibd -t didn't groan
> It does, but you almost certainly ran shibd -t as an identity that did have access and not the shibd user that didn't. But it was most certainly logging it under normal operation.


The shibd -t thing makes sense - I was running it as root (no doubt 
contrary to something I failed to read on the wiki...)

You're right - it was logging. My theory is I missed it because I was 
tail -f'ing the logs while trying to log in, whereas the error is logged 
on startup.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://shibboleth.net/pipermail/users/attachments/20250618/0ad783f7/attachment.htm>