shibsp::ConfigurationException error

[Mike De Lise]

Ok I adjusted the entityID in the idp-metadata.xml and made it match the SSO.
idp-metadata.xml

<md:EntityDescriptor xmlns:md="urn:oasis:names:tc:SAML:2.0:metadata"
ID="_c2da58f00807bc9e89482387c85439c6a67394e4"
entityID="https://192.168.0.26/shibboleth">

shibboleth2.xml
<SSO entityID="https://192.168.0.26/shibboleth">
              SAML2 SAML1
            </SSO>


Now the error has changed to

shibsp::ConfigurationException

The system encountered an error at Mon Mar 2 19:17:18 2015

To report this problem, please contact the site administrator at root at localhost.

Please include the following message in any email:

shibsp::ConfigurationException at (https://192.168.0.26/secure)

None of the configured SessionInitiators handled the request


2015-03-02 19:12:53 DEBUG Shibboleth.Listener [4]: dispatching message
(default/Login::run::Shib1SI)
2015-03-02 19:12:53 INFO Shibboleth.SessionInitiator.Shib1 [4]: unable
to locate Shibboleth-aware identity provider role for provider
(https://192.168.0.26/shibboleth)

On Mon, Mar 2, 2015 at 6:59 PM, Kevin Foote <kpfoote at uoregon.edu> wrote:
>
>> On Mar 2, 2015, at 4:48 PM, Mike De Lise <mdelise at gmail.com> wrote:
>>
>> That's exactly what i've done, restarted all three, httpd, tomcat and
>> shibd and i'm trying to hit https://spip/secure in the browser and
>> getting the Unable to locate metadata for identify provider
>> (https://idp-host/idp/shibboleth)
>>
>> Logs indicate same thing, unable to locate metadata for provider
>> https;//idphost/idp/shibboleth)
>>
>> SELinux is in Permissive mode.
>>
>> Its gotta be something in my shibboleth2.xml..
>
> So does the entityID in the <SSO> tag match what is found as the entityID in your loaded idp-metadata.xml file ?
> Shibd is running if its telling you that via a httpd request to your web server.
>
> --------
> thanks
>  kevin.foote
>
>
> --
> To unsubscribe from this list send an email to users-unsubscribe at shibboleth.net