Closed mcepl closed 3 years ago
It looks like the test data may need to be updated.
It was updated before to work in 2020.
The test were already updated at https://github.com/onelogin/python3-saml/pull/269
A similar looking failure surfaced again in the past few days. (latest version = 1.15.0)
FAIL: testIsInvalidIssuer (tests.src.OneLogin.saml2_tests.logout_request_test.OneLogin_Saml2_Logout_Request_Test)
Tests the is_valid method of the OneLogin_Saml2_LogoutRequest
----------------------------------------------------------------------
onelogin.saml2.errors.OneLogin_Saml2_ValidationError: Could not validate timestamp: expired. Check system clock.)
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/build/source/tests/src/OneLogin/saml2_tests/logout_request_test.py", line 329, in testIsInvalidIssuer
with self.assertRaisesRegex(Exception, 'Invalid issuer in the Logout Request'):
AssertionError: "Invalid issuer in the Logout Request" does not match "Could not validate timestamp: expired. Check system clock.)"
I see some success on May 3 and failure on May 11 (and today), so I expect expiration happened in that range.
@vcunat It seems some test fails know because some SAML Messages I was using as payloads for the test failed.
Fixed them here: https://github.com/SAML-Toolkits/python3-saml/commit/bd65578e5a21494c89320094c61c1c77250bea33
It looks like the test data may need to be updated again
When building python3-saml 1.10.1 package for openSUSE I get couple of tests failing with
'Could not validate timestamp: expired. Check system clock.'
. We build in completely isolated environment so it is possible that we are missing some resource of the operating system, which is expected, but do you have any idea, what’s missing?Complete log with all details of steps executed and packages used.