SP 2.4.2 connecting to IdP 1.3.1 and missing attributes
Christopher Bongaarts
cab at umn.edu
Fri Mar 30 16:26:23 BST 2012
A frequent cause of this would be if there is a firewall blocking the
SOAP port (typically 8443 TCP) either outbound from the SP or inbound to
the IdP. Since the TCP SYN packets are getting dropped, it manifests as
timeouts at the SP.
On 3/29/2012 1:51 PM, Gordon Capreol wrote:
> In other words, the IdP is taking too long to respond to our request. How can we adjust our SP to accommodate the longer wait times?
>
> ~Gordon
>
> On Mar 29, 2012, at 2:47 PM, Cantor, Scott wrote:
>
>>> Hi Scott - Unfortunately not. I'm trying to determine where/why this time-
>>> out is coming from. Do you think it's on the SP or IdP side? Can you
>>> recommend some tests to pinpoint?
>>
>> The timeout is controlled by you/the SP. The cause of the timeout is by definition that the IdP is exeeding it.
>>
>> -- Scott
>>
>> --
>> To unsubscribe from this list send an email to users-unsubscribe at shibboleth.net
>
> --
> To unsubscribe from this list send an email to users-unsubscribe at shibboleth.net
--
%% Christopher A. Bongaarts %% cab at umn.edu %%
%% OIT - Identity Management %% http://umn.edu/~cab %%
%% University of Minnesota %% +1 (612) 625-1809 %%
More information about the users
mailing list