Closed wojciech-piotrowiak closed 4 years ago
@rwinch @jzheaux Is this defect have a chance to be fixed and released? If yes, can I try and open pull request ?
Yes, @wojciech-piotrowiak, thank you for offering! A pull request would be welcome.
@rwinch @jzheaux PR opened: https://github.com/spring-projects/spring-security-saml/pull/481
Recently noticed such error in our app:
After debugging, realized that it happen when our application having maximum timeout available, which is Integer.MAX_VALUE. It is possible, because WebSSOProfileConsumerImpl accept long as maxAuthenticationAge param. So default skewInSec plus maximum forwardInterval will not fit into integer and it makes a problem for Interval class, as below:
Used latest spring-security-saml2-core:1.0.10.RELEASE, previously used 1.0.3 and that version accepted Integer.MAX_VALUE as timeout.