configuring shibboleth on AWS using ELB

[Deirdre Kirmis]

I finally resolved this. I had configured the target group in AWS to route on port 80 instead of port 443.  Recreating the target group on https/port 443 and reregistering the target to route on port 443 fixed the issue and shib works now.  In case anyone else has the issue or has someone ask! Thanks for all of the responses...this is a helpful group!

Deirdre Kirmis
Technology Services
Arizona State University Library
480-965-7240

-----Original Message-----
From: users <users-bounces at shibboleth.net> On Behalf Of Cantor, Scott
Sent: Tuesday, December 17, 2019 10:21 AM
To: Shib Users <users at shibboleth.net>
Subject: Re: configuring shibboleth on AWS using ELB

On 12/17/19, 12:12 PM, "users on behalf of Deirdre Kirmis" <users-bounces at shibboleth.net on behalf of Deirdre.Kirmis at asu.edu> wrote:

> Also, I think all things are pointing to the fact that I need to add 
> parameters in my <Session> configuration to preserve post data and 
> repost it

Whether you need it or not, that has has nothing to do with what you described. Loss of form data just means the eventual request after a timeout is a GET and not a POST, not that user headers are missing.

> I apologize, I did not realize support was typically only for members 
> of the consortium,

Support from *me* is; the list is full of volunteers who have been responding.

I said something because what Amazon said is likely either wrong, or was mis-translated somewhere.

-- Scott


--
For Consortium Member technical support, see https://urldefense.proofpoint.com/v2/url?u=https-3A__wiki.shibboleth.net_confluence_x_coFAAg&d=DwICAg&c=l45AxH-kUV29SRQusp9vYR0n1GycN4_2jInuKy6zbqQ&r=X1YAM2yWs1HIcWRXyPCSUtCKxhQO748y834uz5ZFnTY&m=nlMUbcVljIcFtNO5G1i3suBYSp40F-iRq5OE4hFrMI4&s=p8h17qxhBQ_iACBFHIe8CyDc_VsKadQXRnT-x5Egliw&e=
To unsubscribe from this list send an email to users-unsubscribe at shibboleth.net