Bug 39774 – document ucs/server/sso/fqdn

Bug 39774 - document ucs/server/sso/fqdn


Summary:	document ucs/server/sso/fqdn

Status:	RESOLVED WONTFIX

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

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

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2015-11-04 10:49 CET by Felix Botner
Modified:	2019-01-03 07:19 CET (History)
CC List:	0 users

See Also:
What kind of report is it?:	---
What type of bug is this?:	---
Who will be affected by this bug?:	---
How will those affected feel about the bug?:	---
User Pain:
Enterprise Customer affected?:
School Customer affected?:
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number:
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 Felix Botner

2015-11-04 10:49:31 CET

see Bug #39574 comment 8

(In reply to Arvid Requate from comment #8)
> IPv6: Ok, fine with me.
> 
> I suggest adjusting the changelog entry to point out that the UCR-Variable
> needs to be adjusted *before* joining a UCS Backup and that this may
> conveniently be done via UDM-UCR-policy. Alternatively we may add an SDB
> article. Currently, nobody has the chance to known how to properly make use
> of this UCR variable without reading the joinscript code and understanding a
> lot about the intricacies of UCS Join.
> 
> "The name can be changed through the &ucsUCRV;
> <envar>ucs/server/sso/fqdn</envar>"
> 
> Either we adjust this sentence or we should not mention it at all and it's
> for internal/project use only.

Comment 1 Stefan Gohmann

2019-01-03 07:19:03 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.