sp-signing-key not recognized after upgrade

[Cantor, Scott]

I'm not specifically familiar with those error codes. Most of the time, it's pretty much down to permissions or the password configured for the private key if it has one (which we don't really encourage since storing a password in plaintext next to a private key on the same disk is pointless).

With Docker involved, whatever it is is probably connected to it somehow. If it were RHEL, I'd say SELinux would be the thing to check, but didn't think Debian had anything along that line.

> Today is the first day I've touched Shibboleth so hopefully
> the solution to this is obvious to someone?

It's never not been the obvious stuff when this kind of thing comes up and usually it's from people who don't have the basic understanding to test for that, which is obviously not the case here.

The versions don't matter, that's all just OpenSSL calls and code that hasn't changed in years.

-- Scott