Troubleshooting the "Unable to decode" (IdP 3.3)

[O'Dowd, Josh]

Sorry, just sent this data, sans the fact that we are running Jetty 9.3.6, behind Apache(SSL), behind Kimp LB

Josh

From: users [mailto:users-bounces at shibboleth.net] On Behalf Of Brent Putman
Sent: Wednesday, August 30, 2017 2:44 PM
To: users at shibboleth.net
Subject: Re: Troubleshooting the "Unable to decode" (IdP 3.3)




On 8/30/17 4:38 PM, O'Dowd, Josh wrote:

Ø  If someone else with a test IdP handy (and who knows what they are doing) can reproduce, that will eliminate operator error.


IdP version 3.3.1 on OpenJDK Runtime Environment (build 1.8.0_131-b11)

What does your actual IdP server environment look like?  Jetty vs Tomcat vs other?  Apache httpd in front?  Load balancer, etc?  Anything else relevant that we can't anticipate to ask you?

Per the other message, I'd suspect something corrupting the request before it gets to the IdP.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://shibboleth.net/pipermail/users/attachments/20170830/19266311/attachment.html>