I am new to Shibboleth and trying to implement it on my small home network.

[Peter Schober]

Zombie Ryushu via users <users at shibboleth.net> [2024-09-30 17:24 CEST]:
> I am using a  Docker Image for the IDP. I generates three keysets using
> OpenSSL signed by my internal CA, idp-encrytion, idp-signing, and
> idp-backchannel.

None of which is necessary for most deployments: Trust into public
keys (as published via SAML Metadata) does not come from X.509
certificate structures (and hence not from your internal CA) but from
using trusted SAML Metadata, cf.
https://shibboleth.atlassian.net/wiki/spaces/CONCEPT/pages/928645130/TrustManagement

> I used a different docker image called idp-shib-ui to setup a small
> webserver to generate the metadata for the SP

You certainly don't need to be using Internet2/Unicon's UI for
Managing the Shibboleth IDP in order to add some SP Metadata to it.
More importantly why would an IDP extension generate SAML Metadata
"for the SP" (and what SP are we talking about here, specifically)?
That's the job of the SP (software, operator) to provide you (as IDP
admin) with SAML Metadata about itself (the SP).

> and then modified it for use on the IDP

Modified how exactly and why was that necessary?

> and well, none of its working.

What kind of answer do you expect from the Shibboleth users community
based on the above "problem statement"?
Whatever one may think of ESR maybe having a look at
"How To Ask Questions The Smart Way"
might prove helpful to you in getting your problems fixed.

-peter