Webisoget not happy with our V4 IdP

Wessel, Keith kwessel at illinois.edu
Thu Feb 11 03:29:26 UTC 2021


It could be Webisoget and the ALB not getting along, but I don't think it's the stickiness. I'm testing that theory, though.

Is the web.xml block responsible for not appending the JSESSIONID to the URL the <session-config> block? Or is it something else that I'm not finding? Just want to make sure I'm pulling out the right thing before I go hacking up my web.xml.

Keith


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

On 2/10/21, 5:30 PM, "users on behalf of Wessel, Keith" <users-bounces at shibboleth.net on behalf of kwessel at illinois.edu> wrote:

>    Thanks, all. I was thinking cookies, too, but Webisoget seems to be handling them properly.

Maybe webisoget is switching server nodes in some way and bypassing the LB's sticky policy.

>    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?

It's a web.xml setting, part of the Java standard, near the bottom, you just yank the rule.

>    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.

I do too.

-- Scott


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


More information about the users mailing list