Odd behavior of the IdP's SAML Metadata endpoint if one sets internal.xml SessionManager time to 60000

[Michael A Grady]

On Dec 10, 2013, at 3:55 PM, Cantor, Scott wrote:

> On 12/10/13, 1:20 PM, "Michael A Grady" <mgrady at unicon.net> wrote:
> 
>> I'm not sure what the "magic number" is that causes the problem, but 70
>> seconds (70000) is working just fine. Certainly nothing critical about
>> this, but seemed worth noting to the list.
> 
> I can't see how this is possible or makes any sense, but you can file a
> bug on it, obviously.
> 
> -- Scott

I certainly agree that it makes no sense, and I also can't think of how it would be possible. I figured I had to have made some other config error, but I can literally just replace the '6' in "60000" with a 7 or 9, restart the IdP, and not have the problem, and then change that '7' or '9' to a '6', restart, and have the problem. So I know that that is absolutely the only thing I've changed.

I'll try to get to a bit more testing -- for example, see if a shorter value than 60000 also results in this, or if some weird way, 60000 is "magic" -- and then file a report. And I'll document it somewhere on the wiki as at least an FYI, once I try a few more values.

--
Michael A. Grady
Senior IAM Consultant, Unicon, Inc.