UnsolicitedSSOConfiguration in relying party

[Lalith Jayaweera]

Thanks

Not sure what triggered us to configure so way back for IDP initiated
relying partys,

Anyway does this mean any relying party configured in IdP 3.2.x can be
accessed via below URL pattern as well,

https://myidp.com/idp/profile/SAML2/Unsolicited/SSO?providerId=https://mysp.coml
<https://idpweb1.vu.edu.au/idp/profile/SAML2/Unsolicited/SSO?providerId=https://askvu.vu.edu.au/ci/openlogin/saml/subject/contact.customfields.sso_id/redirect/app/counsel>

On Thu, Apr 13, 2017 at 11:07 AM, Cantor, Scott <cantor.2 at osu.edu> wrote:

> On 4/12/17, 9:01 PM, "users on behalf of Lalith Jayaweera" <
> users-bounces at shibboleth.net on behalf of ljayaweera at gmail.com> wrote:
>
> > In IdP 2.x, there was a difference where we provide both RelyingParty id
> and provider the same value (SP entity ID) in relying
> > party.xml and then have links like below to access in websites....
>
> No, there wasn't. There is no difference.
>
> > Hence I thought, similar difference in IdP 3.2.x or how/what to to
> modify to cater for this need (IDP Initiated SP).
>
> Whatever you think you were doing, you were not doing or you were doing
> incorrectly.
>
> -- Scott
>
>
>
>
>
> --
> To unsubscribe from this list send an email to
> users-unsubscribe at shibboleth.net
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://shibboleth.net/pipermail/users/attachments/20170413/8ba4ce46/attachment.html>