Shibboleth2->Shibboleth3: relying-party.xml for

ls Lidz lslidzgeneve at gmail.com
Thu Apr 6 17:14:41 EDT 2017


We have a number of vendors whereby we had to configure in the
'relying-party.xml' -- did not work via the conventional methodology
(InCommon).

Would anyone have an idea on how toI migrate the following Shibv2 example
to Shibv3?

Will it still reside in the 'relying-party.xml' file?  Would the format
change in any way?

    <!-- relying party for service-now -->

    <rp:RelyingParty id="https://example.com"

                  provider="https://idp_entity_id/idp/shibboleth"

                  defaultSigningCredentialRef="IdPCredential">

        <rp:ProfileConfiguration

                xsi:type="saml:SAML2SSOProfile"

                encryptAssertions="never"

                encryptNameIds="never" />

    </rp:RelyingParty>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://shibboleth.net/pipermail/users/attachments/20170406/7c581839/attachment.html>


More information about the users mailing list