Univention Bugzilla – Bug 45720
LDAP login error due to wrong time
Last modified: 2018-03-08 10:56:38 CET
Version: 4.2-2 errata219 (Lesum) Execution of command 'udm/nav/object/query navigation' has failed: Traceback (most recent call last): File "%PY2.7%/notifier/threads.py", line 82, in _run tmp = self._function() File "%PY2.7%/notifier/__init__.py", line 104, in __call__ return self._function( *tmp, **self._kwargs ) File "%PY2.7%/univention/management/console/modules/udm/__init__.py", line 1063, in _thread for module, obj in list_objects(container, object_type=object_type): File "%PY2.7%/univention/management/console/modules/udm/udm_ldap.py", line 1003, in list_objects result = ldap_connection.search(base=container, scope='one') File "%PY2.7%/univention/admin/uldap.py", line 437, in search raise univention.admin.uexceptions.ldapError(_err2str(msg), original_exception=msg) ldapError: Invalid credentials: SASL(-13): authentication failure: condition NotOnOrAfter 2017-11-10T14:57:57Z, current time is 2017-11-10T15:26:05Z
It looks like the system time was changed to wintertime. In case kerberos was used for authorization that might have been the problem.
(In reply to Johannes Keiser from comment #1) > It looks like the system time was changed to wintertime. In case kerberos > was used for authorization that might have been the problem. No, the SAML assertion has just timed out. The time difference is 30 minutes. This might be a duplicate of Bug #44621.
*** This bug has been marked as a duplicate of bug 44621 ***