Issue / Bug with Unsolicited SSO after Update from IdP 3.3.1 to 3.4.3

[Tom Scavo]

On Tue, Mar 12, 2019 at 9:11 AM Cantor, Scott <cantor.2 at osu.edu> wrote:
>
> On 3/12/19, 7:02 AM, "users on behalf of Martin Lunze" <users-bounces at shibboleth.net on behalf of martin.lunze at tu-dresden.de> wrote:
>
> > My test-call looks like this:
>
> You can't use curl like that unless you're also handling cookies with it. That isn't new, and has nothing to do with the upgrade. All it will do is redirect into a flow, fail to send back JSESSIONID, and trigger the exact error you got.

Here's a cookbook how to use curl to obtain a SAML2 response from a
Shibboleth IdP. Last time I tried this, four round trips were
required.

https://spaces.at.internet2.edu/x/8QKRAg

HTH,

Tom