Univention Bugzilla – Bug 39921
Single sign on fails if server has time in the past
Last modified: 2022-05-09 17:36:13 CEST
When trying to single sign on on a DC slave with a date in the past the following traceback occurs: The server encountered an unexpected condition which prevented it from fulfilling the request. Traceback (most recent call last): File "/usr/lib/python2.7/dist-packages/cherrypy/_cprequest.py", line 656, in respond response.body = self.handler() File "/usr/lib/python2.7/dist-packages/cherrypy/lib/encoding.py", line 188, in __call__ self.body = self.oldhandler(*args, **kwargs) File "/usr/lib/python2.7/dist-packages/cherrypy/_cpdispatch.py", line 34, in __call__ return self.callable(*self.args, **self.kwargs) File "/usr/sbin/univention-management-console-web-server", line 1141, in index return acs(binding, message, relay_state) File "/usr/sbin/univention-management-console-web-server", line 1151, in attribute_consuming_service response = self.acs(message, binding) File "/usr/sbin/univention-management-console-web-server", line 1261, in acs response = self.sp.parse_authn_request_response(message, binding, self.outstanding_queries) File "/usr/lib/python2.7/dist-packages/saml2/client_base.py", line 573, in parse_authn_request_response binding, **kwargs) File "/usr/lib/python2.7/dist-packages/saml2/entity.py", line 949, in _parse_response response = response.verify(key_file) File "/usr/lib/python2.7/dist-packages/saml2/response.py", line 853, in verify res = self._verify() File "/usr/lib/python2.7/dist-packages/saml2/response.py", line 391, in _verify assert self.issue_instant_ok() AssertionError
Created attachment 7372 [details] patch Patch, which displays a user friendly error message.
This issue has been filled against UCS 4.1. The maintenance with bug and security fixes for UCS 4.1 has ended on 5st of April 2018. Customers still on UCS 4.1 are encouraged to update to UCS 4.3. Please contact your partner or Univention for any questions. If this issue still occurs in newer UCS versions, please use "Clone this bug" or simply reopen the issue. In this case please provide detailed information on how this issue is affecting you.
fixed via git:6247389ecdaf818985737d764d018aa0b692066f