From 1d670c398780843ee6b79ffef8fb443962079804 Mon Sep 17 00:00:00 2001 From: msweet Date: Fri, 26 Jul 2013 21:07:52 +0000 Subject: [PATCH] Fix typos in examples - CUPS-Add-Modify-xxx instead of CUPS-Add-xxx. git-svn-id: svn+ssh://src.apple.com/svn/cups/cups.org/trunk@11200 a1ca3aef-8c08-0410-bb20-df032aa958be --- doc/help/policies.html | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/doc/help/policies.html b/doc/help/policies.html index 18f4c80e9..42b789aaf 100644 --- a/doc/help/policies.html +++ b/doc/help/policies.html @@ -39,7 +39,7 @@ HREF="ref-cupsd-conf.html#LimitIPP">Limit subsections which list th 7 8 # All administration operations require an administrator to authenticate... - 9 <Limit CUPS-Add-Printer CUPS-Delete-Printer CUPS-Add-Class + 9 <Limit CUPS-Add-Modify-Printer CUPS-Delete-Printer CUPS-Add-Modify-Class CUPS-Delete-Class CUPS-Set-Default> 10 AuthType Default 11 Require user @SYSTEM @@ -100,7 +100,7 @@ HREF="ref-cupsd-conf.html#LimitIPP">Limit subsections which list th

The access control rules are listed after the Limit line and are the same as those used for Location sections. In this case, we require the owner of the job ("@OWNER") or a member of the SystemGroup ("@SYSTEM") to do the operation. Because we do not include an AuthType directive here, the user information can come from the IPP request itself or the authenticated username from the HTTP request. The administrative operations starting on line 9, however, do use the AuthType directive, and so administrative operations need to be authenticated:

- 9      <Limit CUPS-Add-Printer CUPS-Delete-Printer CUPS-Add-Class
+ 9      <Limit CUPS-Add-Modify-Printer CUPS-Delete-Printer CUPS-Add-Modify-Class
       CUPS-Delete-Class CUPS-Set-Default>
 10        AuthType Default
 11        Require user @SYSTEM
-- 
2.39.2