Webisoget not happy with our V4 IdP

[Wessel, Keith]

Thanks, all. I was thinking cookies, too, but Webisoget seems to be handling them properly. Jim, the -cache option to Webisoget is only used between runs, right? As long as Webisoget is running in -continue mode, it keeps the cookies in memory and continues to send them with subsequent requests, right?

Scott, is there any way to temporarily change the behavior to have the JSESSIONID be passed back as part of the URL to test that theory in V4?

And thanks, Paul, for the sample test script. You're not using -cache, and it works. So, I'm suspecting it's something with the AWS ALB. It's not the form input file because we're not getting far enough to have a form to fill out. It's when I should be getting the login form that I'm getting the error.

Keith


-----Original Message-----
From: users <users-bounces at shibboleth.net> On Behalf Of Cantor, Scott
Sent: Wednesday, February 10, 2021 4:03 PM
To: Shib Users <users at shibboleth.net>
Subject: Re: Webisoget not happy with our V4 IdP

You have a cookie issue, the NoSuchFlowExecutionException is just due to not receiving JSESSIONID back to line up with the flow execution key on the URL.

It's nothing to do with V4 and the password flow always checks for Basic Auth credentials, that's why ECP works.

What I might guess perhaps is that your old container was configured to pass the JSESSIONID back on the URL and that was being handled, whereas the V4 web.xml default is to block that.

-- Scott


-- 
For Consortium Member technical support, see https://urldefense.com/v3/__https://wiki.shibboleth.net/confluence/x/coFAAg__;!!DZ3fjg!olmuS8_jIZPZVzHt2uO8PnUIGgpEdJ_9egyuML5IGYO1EWccbhhYnHirXdeDP47OKQ$ 
To unsubscribe from this list send an email to users-unsubscribe at shibboleth.net