Bug 48417 – admember.py has problems if the server-domain is different from the ad domain

Bug 48417 - admember.py has problems if the server-domain is different from the ad domain


Summary:	admember.py has problems if the server-domain is different from the ad domain

Status:	RESOLVED WONTFIX

Product:	UCS
Classification:	Unclassified
Component:	Password changes
Version:	UCS 4.3
Hardware:	Other Linux

Importance:	P5 enhancement (vote)
Target Milestone:	---
Assigned To:	UCS maintainers
QA Contact:	UCS maintainers

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2019-01-03 11:01 CET by Stephan Hendl
Modified:	2021-05-14 16:34 CEST (History)
CC List:	6 users (show)

See Also:
What kind of report is it?:	Feature Request
What type of bug is this?:	4: Minor Usability: Impairs usability in secondary scenarios
Who will be affected by this bug?:	2: Will only affect a few installed domains
How will those affected feel about the bug?:	---
User Pain:
Enterprise Customer affected?:	Yes
School Customer affected?:
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number:	2016111021000196
Bug group (optional):	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 Stephan Hendl 2019-01-03 11:01:16 CET

+++ This bug was initially created as a clone of Bug #42964 +++

admember.py seems to work with: "dig $nameserver $(ucr get domainname) +short" - that returns the expected ip-address of the ad-dc if it is responsible for the DNS-Zone that matches with $(ucr get domainname). 

Customer Environment:
AD/Samba-Domain: bla.foo.bar
Serverdomain: cat.foo.bar

A server-password-change is not possible with this setting. Maybe admember.py can work with Service-Records to determine the AD DC?

Comment 1 Stephan Hendl 2019-01-03 11:02:23 CET

The problem still exists. I changed the component into "Password changes" - maybe that's not the correct one...

Comment 2 Ingo Steuwer

2021-05-14 15:43:08 CEST

This issue has been filed against UCS 4.3.

UCS 4.3 is out of maintenance and many UCS components have changed in later releases. Thus, this issue is now being closed.

If this issue still occurs in newer UCS versions, please use "Clone this bug" or reopen it and update the UCS version. In this case please provide detailed information on how this issue is affecting you.