Bug 40597 – "Account information"->"Organization name" vs domain name

Bug 40597 - "Account information"->"Organization name" vs domain name


Summary:	"Account information"->"Organization name" vs domain name

Status:	REOPENED

Product:	UCS
Classification:	Unclassified
Component:	System setup
Version:	UCS 4.4
Hardware:	Other Linux

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

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2016-02-08 09:56 CET by Felix Botner
Modified:	2019-02-04 18:47 CET (History)
CC List:	2 users (show)

See Also:	45945
What kind of report is it?:	Bug Report
What type of bug is this?:	6: Setup Problem: Issue for the setup process
Who will be affected by this bug?:	2: Will only affect a few installed domains
How will those affected feel about the bug?:	3: A User would likely not purchase the product
User Pain:	0.206
Enterprise Customer affected?:
School Customer affected?:
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number:
Bug group (optional):	External feedback, Usability
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

2016-02-08 09:56:33 CET

If i use "my.domain" as "Account information"->"Organization name" the actual domain becomes "my-domain.intranet".

This is not very intuitive and leads to confusion.
What is "Organization name" anyway?
What is it good for?

Note, not such a big deal, because the domain name be changed in the FQDN settings on "Host settings" page.

Maybe we should explicitly ask for a domain name (instead of "Organization name")?

See, ticket 2016012621000701

Comment 1 Alexander Kläser

2016-02-09 16:44:41 CET

"Organization name" had been added just for convenience in order to generate an appropriate domain name + LDAP base automatically. The idea was that it would be easier to ask somebody for the name of an organization than a domain name. Pre-configuring a domain name (e.g., randomly), it would probably not be changed be someone being less familiar with the concept of a domain.

It is true that it also lead in some usability tests to a bit of confusion - people thought they would need to log in with their "Organization name" as user name. I am not sure whether it would be better to remove it or leave it.

Comment 2 Florian Best

2016-02-09 17:51:36 CET

The field is also used to create the Organization field of the SSL certificates.

Comment 3 Alexander Kläser

2016-02-10 10:07:59 CET

(In reply to Florian Best from comment #2)
> The field is also used to create the Organization field of the SSL
> certificates.

Oh yes, thanks for the remark, I have overseen that.

Comment 4 Florian Best

2017-11-30 11:48:30 CET

It is a common problem in our usability studies.

Comment 5 Florian Best

2017-12-22 14:48:45 CET

See also Bug #45945.

Comment 6 Stefan Gohmann

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