Bug 45720 - LDAP login error due to wrong time
LDAP login error due to wrong time
Status: RESOLVED DUPLICATE of bug 44621
Product: UCS
Classification: Unclassified
Component: UMC - Domain management (Generic)
UCS 4.2
Other Linux
: P5 normal (vote)
: ---
Assigned To: UMC maintainers
UMC maintainers
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2017-11-15 17:44 CET by Johannes Keiser
Modified: 2018-03-08 10:56 CET (History)
2 users (show)

See Also:
What kind of report is it?: Bug Report
What type of bug is this?: 4: Minor Usability: Impairs usability in secondary scenarios
Who will be affected by this bug?: 1: Will affect a very few installed domains
How will those affected feel about the bug?: 2: A Pain – users won’t like this once they notice it
User Pain: 0.046
Enterprise Customer affected?:
School Customer affected?:
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number: 2017111021000505
Bug group (optional): Error handling, External feedback
Max CVSS v3 score:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Johannes Keiser univentionstaff 2017-11-15 17:44:28 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
Comment 1 Johannes Keiser univentionstaff 2017-11-15 17:57:36 CET
It looks like the system time was changed to wintertime. In case kerberos was used for authorization that might have been the problem.
Comment 2 Florian Best univentionstaff 2017-11-15 18:18:11 CET
(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.
Comment 3 Jürn Brodersen univentionstaff 2018-03-08 10:56:38 CET

*** This bug has been marked as a duplicate of bug 44621 ***