IdP custom handling for throttling misbehaving looping SPs

[Russell Beall]

Has anyone implemented any custom code which can detect and throttle, or error out, occurrences of an SP which is misconfigured and starts looping?  We have a couple that get into this condition some of the time and I would rather the user get an error page than an endless loop.  We have seen a single user entirely clog the IdP by opening numerous looping windows, so I would like to prevent that as well.

I had expected it would be easy to find some firewall configuration, perhaps for mitigating DOS attacks, which could detect an IP consuming too much bandwidth or making too many requests over a period of time, and could at least throttle it, but I haven't actually succeeded in that search.

Any pointers would be appreciated.

(I remember asking this question before, and I got a firewall pointer or two, but I wonder if there has been anything more done since then).

Regards,
Russ.