coheigea opened a new pull request, #3699: URL: https://github.com/apache/cxf/pull/3699
…tion SAMLSSOResponseValidator checked an assertion for a replay, and cached its ID, while validating each of its Bearer Subject Confirmations. So an assertion with more than one was rejected as a replay of itself: the first Subject Confirmation cached the ID, and the second then found it in the cache. Check for a replay once per assertion instead, once all of its Bearer Subject Confirmations have been validated, and cache the ID until the latest of their NotOnOrAfter times, as SamlOAuthValidator does. The check now also comes after the audience restriction check, so that only an otherwise valid assertion is cached. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
