configuring shibboleth on AWS using ELB
Deirdre.Kirmis at asu.edu
Tue Dec 17 12:12:08 EST 2019
Thank you so much, Scott(s)...I appreciate your responses. I have the SAML Tracer installed and will get the traces from both configurations and look through them, as you suggested.
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...just have to figure out how to do that. I found this: https://wiki.shibboleth.net/confluence/display/SP3/CommonErrors and have been looking at the section "HTTP POST form data is lost when Shibboleth session expired or does not exist yet".
I apologize, I did not realize support was typically only for members of the consortium, which it looks like our organization is not part of (I'm surprised)! I appreciate all of the help that I've gotten so far anyway!
Arizona State University Library
From: users <users-bounces at shibboleth.net> On Behalf Of Scott Koranda
Sent: Tuesday, December 17, 2019 9:20 AM
To: Shib Users <users at shibboleth.net>
Subject: Re: configuring shibboleth on AWS using ELB
> I am still struggling with this and trying to get it working.
> Shibboleth works perfectly on my server until I put it behind an AWS
> load balancer. Posting my configs, and wondering if anyone sees
> anything that could be causing an issue? I appreciate any suggestions.
If I were to debug your issue, I would start by installing the SAML Tracer plugin in my web browser. It is available for both Firefox and for Chrome.
Then I would start with a clean browser (no history, no sessions, no cookies at all) and go through an entire flow and record it with SAML Tracer. I would do that first for the deployment without the AWS load balancer.
You can export the trace from the plugin and save it to a file, and then later reload it from that file.
Next I would do the same thing (again from a clean browser) but this time for the deployment with the AWS load balancer. I would again save the trace to a file.
I would then compare the two traces line by line and look for differences. I would pay special attention to cookies being set in the responses and which cookies are then sent back upstream. I would also compare the SAML assertions to the extent that I could (if the IdP encrypts the assertion you will not be able to see all of it in SAML Tracer, but you should be able to examine the envelope).
If when comparing the two traces nothing jumps out at you, you could post them (they are just JSON files) somewhere where community members on this list could download them and examine them (pastebin.com, or a GitHub gist, or whatever would be easy). If you do that, however, be aware that you need to first scrub your password from the JSON trace--it is often recorded if your password is sent upstream to the IdP via a normal POST.
I find this approach helpful, in addition to looking at log files, since it records all the details of the back and forth between your web browser and the IdP and SP.
My apologies if I am telling you things you already know or have tried...
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=yLdpfqsm5tajiZigtPMEcyFgh1lxsdMoxjyqcHTdPnY&s=f-n0KfNWUX5uhbEtUhNGqO7NIVT3C3Wej8zv06cvEJw&e=
To unsubscribe from this list send an email to users-unsubscribe at shibboleth.net
More information about the users