Bug 54055 - UMC Operationset for settings/usertemplate is missing
UMC Operationset for settings/usertemplate is missing
Status: RESOLVED DUPLICATE of bug 37927
Product: UCS
Classification: Unclassified
Component: UMC - Domain management (Generic)
UCS 4.4
Other Linux
: P5 normal (vote)
: ---
Assigned To: UMC maintainers
UMC maintainers
:
Depends on: 37927
Blocks:
  Show dependency treegraph
 
Reported: 2021-11-14 17:07 CET by Michael Grandjean
Modified: 2022-06-30 11:10 CEST (History)
6 users (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?: 2: A Pain – users won’t like this once they notice it
User Pain: 0.046
Enterprise Customer affected?:
School Customer affected?: Yes
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number:
Bug group (optional): External feedback, Troubleshooting, Usability
Max CVSS v3 score:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Michael Grandjean univentionstaff 2021-11-14 17:07:35 CET
Still true for 4.4
Didn't check for 5.0

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

2015022421000723

There is no UMC Operationset that allows udm/get with "settings/usertemplate"-flavor which is needed if one wants to use usertemplates.

udm settings/umc_operationset create --position "cn=operations,cn=UMC,cn=univention,$(ucr get ldap/base)" \
    --set name="udm-usertemplates" \
    --set operation="udm/get" \
    --set flavor="settings/usertemplate" \
    --set description="User templates"


Without this permission, users will get a 403 Forbidden after selection a user template in UMC:
---
You are not authorized to perform this action.

Server error message:

Forbidden
---
Comment 1 Florian Best univentionstaff 2022-06-30 11:10:09 CEST

*** This bug has been marked as a duplicate of bug 37927 ***