Bug 44512 – When in MS-AD Membermode the DNS-Hostrecord 'ucs-sso' is not added to the Zone (in AD)

Bug 44512 - When in MS-AD Membermode the DNS-Hostrecord 'ucs-sso' is not added to the Zone (in AD)


Summary:	When in MS-AD Membermode the DNS-Hostrecord 'ucs-sso' is not added to the Zon...

Status:	RESOLVED WONTFIX

Product:	UCS
Classification:	Unclassified
Component:	SAML
Version:	UCS 4.2
Hardware:	Other Linux

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

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2017-05-02 12:25 CEST by Nico Stöckigt
Modified:	2020-07-03 20:54 CEST (History)
CC List:	1 user (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?:	1: Nuisance – not a big deal but noticeable
User Pain:	0.023
Enterprise Customer affected?:	Yes
School Customer affected?:
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number:	2017041921000128
Bug group (optional):
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 Nico Stöckigt

2017-05-02 12:25:27 CEST

When UCS is joined into a MS-AD with SyncMode:READ, relevant DNS-Entries should be synchronized to MS-AD nevertheless. This is an issue especially with Records like 'ucs-sso' and seems not to be a big deal.

Comment 1 Arvid Requate

2017-05-02 13:06:05 CEST

IMHO the tools that create the records should add the record properly themselves (nsupdate) in case of ad/member=yes. Otherwise we will get a zoo of "read-only with exception of xyz" options, complicating the S4-Connector.

Comment 2 Arvid Requate

2017-05-02 13:08:07 CEST

Or the ad/member setup should do it, I don't know the lifetime details of this 'ucs-sso' record.

Comment 3 Ingo Steuwer

2020-07-03 20:54:15 CEST

This issue has been filed against UCS 4.2.

UCS 4.2 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.