shibsp::ConfigurationException error

[Mike De Lise]

Thanks for the response, I guess i'm not too sure what I need to do
about the metadata then,  I've followed the guide and thought it would
use default metadata,  Could you point me in the right direction of
what simple metadata should look like on each server and where it
should be located?

On Mon, Mar 2, 2015 at 2:31 PM, Cantor, Scott <cantor.2 at osu.edu> wrote:
> On 3/2/15, 3:15 PM, "Mike De Lise" <mdelise at gmail.com> wrote:
>>
>>The weird thing is, last night I was getting
>>opensaml:saml2md:MetadataException Unable to locate metadata for
>>identity provider.
>
> It's a related error that just doesn't come up often, you now have
> metadata but it's wrong. There are no IDPSSODescriptor roles present with
> the right protocol constants in them to use.
>
>>shibd.log shows
>>
>>2015-03-02 13:47:05 DEBUG Shibboleth.Listener [2]: dispatching message
>>(default/Login::run::SAML2SI)
>>2015-03-02 13:47:05 INFO Shibboleth.SessionInitiator.SAML2 [2]: unable
>>to locate SAML 2.0 identity provider role for provider
>>(https://10.10.0.37/idp/shibboleth)
>>2015-03-02 13:47:05 DEBUG Shibboleth.Listener [2]: dispatching message
>>(default/Login::run::Shib1SI)
>>2015-03-02 13:47:05 INFO Shibboleth.SessionInitiator.Shib1 [2]: unable
>>to locate Shibboleth-aware identity provider role for provider
>>(https://10.10.0.37/idp/shibboleth)
>
> They're on INFO because neither protocol is required in any given case,
> but collectively that's the error. It tries to issue requests using each
> protocol it knows about and then gives up. The metadata for the IdP is
> wrong, basically.
>
> -- Scott
>
> --
> To unsubscribe from this list send an email to users-unsubscribe at shibboleth.net