Troubleshooting the "Unable to decode" (IdP 3.3)

[O'Dowd, Josh]

Sorry for the typo:
173.252.95.0/255

Josh

-----Original Message-----
From: users [mailto:users-bounces at shibboleth.net] On Behalf Of O'Dowd, Josh
Sent: Friday, August 25, 2017 11:37 AM
To: Shib Users <users at shibboleth.net>
Subject: RE: Troubleshooting the "Unable to decode" (IdP 3.3)

> That's a Shibboleth SP request (that's my relay state convention). If Facebook is using my code, I will be shocked, somewhat pissed off, and maybe amused all at the same time.

I don't know.  Maybe FB leases IP's to other services.  What I do know is that all of these bad requests are coming in from the 173..252.95.0/255 subnet, namely ...8-15, which all come up Facebook, Inc. on a whois.  I don't know whether we can take it for granted that it's FB systems that are using these IPs, and I can't see any SP metadata due to the fact that ALL of the requests coming from these IPs are failures; not a single valid one.

Josh

-- 
To unsubscribe from this list send an email to users-unsubscribe at shibboleth.net