Keep getting InvalidProfileConfiguration

Paul Caskey pcaskey at
Mon May 27 17:56:32 EDT 2019

The files in the test-compose folder are meant as an example.

The idp and so in that directory are pre-wired to trust each other.

If you change anything they won't work, but they are still useful as an example...

Sent from Nine<>
From: Karthikeyan Sundararajan <karthikeyan.s at>
Sent: Monday, May 27, 2019 3:41 PM
To: users at
Subject: Keep getting InvalidProfileConfiguration

I have deployed shibboleth tier docker containers.

I configured my server ip address in sp congratulation files. Then I get login page and when I type username and password it redirects to<>.

So now I modified<> to the same ip address as both sp and idp are running in same host.

However, I keep getting the below message, even after i added it into relyingpartyids,

shib-idp;idp-process.log;dev;nothing;2019-05-27 20:33:13,391 - INFO [org.opensaml.saml.common.binding.impl.SAMLMetadataLookupHandler:129] - Message Handler:  No metadata returned for https://x.x.x.x/shibboleth in role {urn:oasis:names:tc:SAML:2.0:metadata}SPSSODescriptor with protocol urn:oasis:names:tc:SAML:2.0:protocol
shib-idp;idp-process.log;dev;nothing;2019-05-27 20:33:13,480 - WARN [net.shibboleth.idp.profile.impl.SelectProfileConfiguration:117] - Profile Action SelectProfileConfiguration: Profile is not available for RP configuration shibboleth.UnverifiedRelyingParty (RPID https://x.x.x.x/shibboleth)

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <>

More information about the users mailing list