Unable to locate metadata

[Peter Schober]

* Julien Cochennec <julien.cochennec at ac-orleans-tours.fr> [2020-09-23 15:04]:
> [mod_shib:error] [pid 46:tid [client 172.19.0.6:59308] Unable to locate
> metadata for identity provider (http://idp.docker.localhost/idp/shibboleth)

Take an ordinary VM and install the SP on it. Try to make it load
metadata: You give it a file (or directory) and it loads it. Done.
All issues beyond that are results of your specific deployment which
is not software/configuration shipped or supported by this project.

* Julien Cochennec <julien.cochennec at ac-orleans-tours.fr> [2020-09-23 16:38]:
> Those messages seems to be written by shibd, when I look into shibd.log in
> the docker container, I see those messages, and also this.
> 
> I'd like to have more details about the unlocated metadata.
> 
> [root at cc401110ee9b /]# tail /var/log/shibboleth/shibd.log
> 2020-09-23 12:54:55 ERROR OpenSSL : error code: 33558530 in bss_file.c, line
> 402
> 2020-09-23 12:54:55 ERROR OpenSSL : error data:
> fopen('/run/secrets/sp_key','r')
> 2020-09-23 12:54:55 ERROR OpenSSL : error code: 537346050 in bss_file.c,
> line 404
> 2020-09-23 12:54:55 CRIT Shibboleth.Application : error building
> CredentialResolver: Unable to load private key from file
> (/run/secrets/sp_key).

Well, you can't ignore that error above. I know nothing about Docker's
(mis-)use of the FHS but I certainly wouldn't put a private key into /run.

All of this depends on how the image was built and how the container
was run. The Shibboleth project cannot possibly support every packaged
version of its software that someone put together.

-peter