Bug 32009 - Cups printer moderation
Cups printer moderation
Status: RESOLVED WONTFIX
Product: UCS@school
Classification: Unclassified
Component: Print services
UCS@school 3.1 R2
Other Linux
: P5 enhancement (vote)
: UCS@school 3.x
Assigned To: UCS@school maintainers
:
Depends on: 31902 32055
Blocks:
  Show dependency treegraph
 
Reported: 2013-07-18 11:31 CEST by Erik Damrose
Modified: 2019-02-05 21:26 CET (History)
2 users (show)

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

Note You need to log in before you can comment on or make changes to this bug.
Description Erik Damrose univentionstaff 2013-07-18 11:31:00 CEST
In the scope of Bug #31902 support was added for printer restrictions from the computerroom module to work with cups printers. 

The current implementation only supports restricting access, not allowing it, as the implementation of permissions for univention-printserver would have been to big for an errata. Overriding printer restrictions (user, group) and allowing printing from certain ip addresses should be implemented.

Denying access to cups printers is currently done by calls to univention-lpadmin, which modifies the Printer object. From there on the permissions can only be strictened, not relaxed.
The approach was to model the access permissions completely with cups printer policies, however, it is only possible to grant users access with a policy, not deny it.

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

The UCC integration into UCS@school should also cover the printer moderation.
Comment 1 Sönke Schwardt-Krummrich univentionstaff 2019-02-05 21:26:21 CET
This issue has been filled against UCS@school 3.2. The maintenance with
bug and security fixes for UCS@school 3.2 has ended on Dec 31, 2016.

Customers still on UCS 3.x are encouraged to update to UCS 4.3 (or later). 
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.