Bug 56012 - Regression: Server password change doesn't work in AD membermode
Regression: Server password change doesn't work in AD membermode
Status: RESOLVED DUPLICATE of bug 55940
Product: UCS
Classification: Unclassified
Component: Samba
UCS 5.0
Other Linux
: P5 normal (vote)
: ---
Assigned To: Samba maintainers
Samba maintainers
:
Depends on: 54390
Blocks:
  Show dependency treegraph
 
Reported: 2023-04-24 15:09 CEST by Arvid Requate
Modified: 2023-04-24 15:09 CEST (History)
8 users (show)

See Also:
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?: Yes
School Customer affected?:
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number: 2023042121000077
Bug group (optional): bitesize
Max CVSS v3 score:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Arvid Requate univentionstaff 2023-04-24 15:09:06 CEST
The change for Bug #54390 moved the code for chancing the password of a samba memberserver out of

/usr/lib/univention-server/server_password_change.d/univention-samba

to 

/usr/lib/univention-server/server_password_change.d/univention-admember

But that now causes a problem for customers that e.g. have a replica joined to their UCS primary, both in ad/member mode (UCR: samba/role=memberserver and ad/member=true), as the `univention-admember` script is only installed on the server where the AD-Connector is installed (usually the UCS Primary Directory Node).

As a workaround we now copied the univention-admember script to all UCS Replica and  Managed Nodes and manually had to fix the machine secrets of all those systems in samba (otherwise one doesn't get out of that situation again).
Comment 1 Arvid Requate univentionstaff 2023-04-24 15:09:20 CEST

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