Unable to decode incoming request

Michael Dahlberg olgamirth at gmail.com
Thu Mar 15 10:05:08 EDT 2018


You were absolutely correct ... including the endpoint URL.

(My apologies,  I realize you're not being paid to answer emails) Could you
tell me what in my original problem description led you to believe that was
the problem?  I'm asking to try and learn from my mistakes.


On Tue, Mar 13, 2018 at 7:45 PM, Cantor, Scott <cantor.2 at osu.edu> wrote:

> > I thought, from what you said, that once I successfully authenticated,
> they were
> > redirecting me to a different AssertionConsumerService location, than
> the one
> > in their metadata (in my mind, I associate that value with an endpoint).
> Nope.
> > Is there any way to confirm that they are going to the SAML 1 legacy
> endpoint?
> IdP and web server logs. Audit logs. Pretty much every log in different
> ways.
> -- Scott
> --
> For Consortium Member technical support, see https://wiki.shibboleth.net/
> confluence/x/coFAAg
> To unsubscribe from this list send an email to
> users-unsubscribe at shibboleth.net
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://shibboleth.net/pipermail/users/attachments/20180315/cb7695d5/attachment.html>

More information about the users mailing list