Bug 33137 - Only show applicable policy types on policies sub tab of forward/reverse DNS zones
Only show applicable policy types on policies sub tab of forward/reverse DNS ...
Status: NEW
Product: UCS
Classification: Unclassified
Component: UMC - DNS
UCS 5.0
Other Linux
: P5 enhancement (vote)
: UCS 4.x
Assigned To: UMC maintainers
:
: 24650 (view as bug list)
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2013-11-05 17:35 CET by Philipp Hahn
Modified: 2021-04-27 10:50 CEST (History)
4 users (show)

See Also:
What kind of report is it?: Feature Request
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): Cleanup, Usability
Max CVSS v3 score:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Philipp Hahn univentionstaff 2013-11-05 17:35:41 CET
A DNS forward zone allows to add all kind of policies, which don't have any effect on DNS zones, as they store only A/AAAA/CNAME/PTR/SRV/TXT RRs:
Policy: Autostart
Policy: Desktop
Policy: DHCP Allow/Deny
Policy: DHCP Boot
Policy: DHCP DNS
Policy: DHCP Dynamic DNS
Policy: DHCP lease time
Policy: DHCP NetBIOS
Policy: DHCP routing
Policy: DHCP statements
Policy: LDAP server
Policy: Mail quota
Policy: Maintenance
Policy: Master packages
Policy: Member Server packages
Policy: NFS mounts
Policy: Passwords
Policy: Print quota
Policy: Print server
Policy: Release
Policy: Repository server
Policy: Repository synchronisation
Policy: Slave packages
Policy: UMC
Policy: Univention Configuration Registry
Policy: Univention Directory Manager container settings

To improve usability they should be removed/hidden.
Best would be to hide the whole tab [Policies].
Comment 1 Florian Best univentionstaff 2016-02-19 14:04:48 CET
*** Bug 24650 has been marked as a duplicate of this bug. ***
Comment 2 Florian Best univentionstaff 2016-02-19 14:09:12 CET
The reason for this behavior is that zones are also a container.
So this bug is technically invalid.

root@xen3:~# udm users/user create --position zoneName=3.2.1.in-addr.arpa,cn=dns,dc=school,dc=local --set username=blubbb --set lastname=a --set password=univention
Object created: uid=blubbb,zoneName=3.2.1.in-addr.arpa,cn=dns,dc=school,dc=local

But from usability standpoint we should nevertheless hide it!
Comment 3 Philipp Hahn univentionstaff 2021-04-27 10:50:32 CEST
Still with UCS 5.0-0

While LDAP does not put any restriction on containers UDM/UMC should least provide a warning if you put objects in the wrong location. Showing policy setting for a DNS zone, which in 99% of all use cases not appropriate, it at least confusing and leads to bad user experience. GUIs are there to *help* users, not *confuse* them.