SP ACS extra query string parameter rejected by IdPv3, not rejected by IdPv2

[Cantor, Scott]

On 3/12/16, 12:17 PM, "users on behalf of Waldbieser, Carl" <users-bounces at shibboleth.net on behalf of waldbiec at lafayette.edu> wrote:


>
>Our current Shibboleth IdPv2 service seems to accept this slight difference without a problem. 

I really don't know how V2 could have been accepting that, and if it did, it was a bug. I believe I answered that same question a few days ago. There was no response at that time about what V2 actually did and I didn't go looking.

>Which behavior is correct?  IdPv2 being tolerant of the extra parameter, or IdPv3 rejecting it?  Is this a bug in IdPv3, or is this an issue I need to bring up with the service provider?

It's a bug in V2 apparently, though I don't know how that's possible at this late a date. People have encountered this before, so I was fairly certain the behavior wasn't new.

-- Scott