Reason wrote:
> Hi All,
> For Help
> When I accessed the page protected by SP, it redirected to the IdP but an
> erroe occured
> *Error Message: SAML 2 SSO profile is not configured for relying party* *
> https://sp.example.org/shibboleth*
> I have added this relying-party in the *relying-party.xml, *details are as
> fellow
>
> <RelyingParty id="https://sp.example.org/shibboleth"
> provider="https://idp.2288.org:8080/idp/profile"
> defaultAuthenticationMethod="urn:oasis:names:tc:SAML:2.0:ac:classes:PasswordProtectedTransport">
> <ProfileConfiguration xsi:type="saml:ShibbolethSSOProfile" />
> <ProfileConfiguration xsi:type="saml:SAML1AttributeQueryProfile" />
> <ProfileConfiguration xsi:type="saml:SAML1ArtifactResolutionProfile" />
> <ProfileConfiguration xsi:type="saml:SAML2SSOProfile" />
> <ProfileConfiguration xsi:type="saml:SAML2AttributeQueryProfile" />
> <ProfileConfiguration xsi:type="saml:SAML2ArtifactResolutionProfile" />
> </RelyingParty>
>
> What's wrong with my configurarion?
>
> P.S. I use 2.0 IdP
>
--
SWITCH
Serving Swiss Universities
--------------------------
Chad La Joie, Software Engineer, Net Services
Werdstrasse 2, P.O. Box, 8021 Zürich, Switzerland
phone +41 44 268 15 75, fax +41 44 268 15 68
chad....@switch.ch, http://www.switch.ch
Reason wrote:
> Sorry, I commented the <MetadataProvider> in *relying-party.xml....*
Reason wrote:
> I have a question, maybe very simple
> in SP's configuration file:*shibboleth2.xml*, it has an item
> <MetaDataProvider>
> in IdP's configuration file:*relying-party.xml, *it also has an item
The concept is, and the underlying metadata profiles(s) are the same, but not the configuration element itself.
-- Scott