Bug 42763 – GSSAPI Error: The context has expired (Success)

Bug 42763 - GSSAPI Error: The context has expired (Success)


Summary:	GSSAPI Error: The context has expired (Success)

Status:	RESOLVED WONTFIX

Product:	UCS
Classification:	Unclassified
Component:	AD Connector
Version:	UCS 4.1
Hardware:	Other Linux

Importance:	P5 normal (vote)
Target Milestone:	---
Assigned To:	Samba maintainers
QA Contact:

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2016-10-25 16:23 CEST by Florian Best
Modified:	2019-01-03 07:18 CET (History)
CC List:	1 user (show)

See Also:	38285
What kind of report is it?:	Bug Report
What type of bug is this?:	6: Setup Problem: Issue for the setup process
Who will be affected by this bug?:	1: Will affect a very few installed domains
How will those affected feel about the bug?:	3: A User would likely not purchase the product
User Pain:	0.103
Enterprise Customer affected?:
School Customer affected?:
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number:	2016102021000151, 2016101521000198
Bug group (optional):	Error handling, External feedback
Max CVSS v3 score:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Florian Best

2016-10-25 16:23:09 CEST

We received the following feedback from two different systems:

Configuring Active Directory connection: {'info': 'SASL(-1): generic failure: GSSAPI Error:  The context has expired (Success)', 'desc': 'Local error'}

Version: 4.1-3 errata293 (Vahr)
Version: 4.1-3 errata292 (Vahr)

Remark: Simply running install

Comment 1 Stefan Gohmann

2019-01-03 07:18:24 CET

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.