Shibboleth AA timed out

[Cantor, Scott]

On 2/21/12 5:33 PM, "XiaoXia Dong" <x-dong at northwestern.edu> wrote:
>
>I looked at the logs a little more closer now and I have a new theory. It
>looks like that the user got a timeout because there is another request
>coming in in the middle of retrieving of attributes for this troubled
>user.
>  And shibboleth finished next connections first, then coming back to the
>first connection. So the first one got a response within 1 minute and 20
>seconds. Could this be something wrong with my set up for Shibboleth IdP
>1.3? Have you ever seen something like this before? Thanks.

The old IdP is multi-threaded, it doesn't serialize requests. It doesn't
work the way you're suggesting. If your queries take that long, then your
source of data is simply too slow or your server is overloaded handling
its workload.

I don't have to tell you either that you need to get off of Shibboleth
1.3. It is no longer either supported and is vulnerable to security
issues. If you can't upgrade Shibboleth, then you should be looking at
different software options.

-- Scott