"no signing credential resolved, leaving message unsigned"

[Cantor, Scott]

> 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.

-- Scott