Bug 50705

Summary:	After an update the "auth methods" are not used ore applied anymore.
Product:	UCS	Reporter:	Christina Scheinig <scheinig>
Component:	Samba4	Assignee:	Samba maintainers <samba-maintainers>
Status:	NEW ---	QA Contact:	Samba maintainers <samba-maintainers>
Severity:	normal
Priority:	P5	CC:	bremer, gulden, heidelberger, steuwer
Version:	UCS 4.4
Target Milestone:	---
Hardware:	Other
OS:	Linux
URL:	https://help.univention.com/t/problem-after-an-update-the-auth-methods-are-not-used-or-applied/13567
See Also:	https://forge.univention.org/bugzilla/show_bug.cgi?id=49663 https://forge.univention.org/bugzilla/show_bug.cgi?id=47314 https://forge.univention.org/bugzilla/show_bug.cgi?id=47392
What kind of report is it?:	Bug Report	What type of bug is this?:	5: Major Usability: Impairs usability in key scenarios
Who will be affected by this bug?:	1: Will affect a very few installed domains	How will those affected feel about the bug?:	5: Blocking further progress on the daily work
User Pain:	0.143	Enterprise Customer affected?:
School Customer affected?:	Yes	ISV affected?:
Waiting Support:		Flags outvoted (downgraded) after PO Review:	Yes
Ticket number:	2019110821000702, 2020011021000269, 2020031621000647	Bug group (optional):
Max CVSS v3 score:

Description Christina Scheinig

2020-01-10 11:20:09 CET

In Bug 47314 we fixed the problem, that cross-domain samba share access via same user+password doesn’t work any more on UCS memberservers which are joined into a UCS Samba/AD domain.

A customer now ran in the situation twice, that after an update the ucr variable samba/global/options/"auth methods"
has to be set again (it is still set but not recognized from samba after the update). 
Without setting the ucrV again the shares on the memberservers are not accessable anymore.

Comment 1 Nico Gulden

2020-04-17 14:28:00 CEST

How can this be reproduced?

Comment 3 Nico Gulden

2020-04-20 12:31:52 CEST

In Ticket#2019110821000702 it occurred with UCS 4.4-2 with UCS@school installed. In both tickets it was reported, it occurred after an UCS upgrade. It happened at one customer only so far.