{"id":810,"date":"2011-05-08T12:04:00","date_gmt":"2011-05-08T10:04:00","guid":{"rendered":"http:\/\/doenges.com\/blog\/2011\/05\/08\/tech-tip-soving-the-need-to-authenticate-a-print-operator-to-change-printer-settings-on-mac-os-x-10-6"},"modified":"2011-05-08T12:04:00","modified_gmt":"2011-05-08T10:04:00","slug":"tech-tip-soving-the-need-to-authenticate-a-print-operator-to-change-printer-settings-on-mac-os-x-10-6","status":"publish","type":"post","link":"https:\/\/doenges.com\/blog\/2011\/05\/08\/tech-tip-soving-the-need-to-authenticate-a-print-operator-to-change-printer-settings-on-mac-os-x-10-6","title":{"rendered":"Tech Tip: Soving the need to Authenticate a &#8220;Print Operator&#8221; to Change Printer Settings on Mac OS X 10.6"},"content":{"rendered":"<p>On Mac OS X 10.6 (Snow Leopard) a non-administrator user can not change all settings of the installed printers. This is really annoying when a printer error causes the print queue to go on hold: the user can not resume printing when the problem has been solved. Instead, a dialog pops up asking for the user name and password of a member of the &#8220;<i>Print Operators<\/i>&#8221; group. Usually, that means a system administrator has to manually enter the credentials before the user can resume working.<\/p>\n<p>The problem is caused by the fact that only members of the group\u00a0&#8220;<i>Print Operators<\/i>&#8221; are allowed to control the printer. Normal users (i.e. members of the group\u00a0&#8220;<i>Staff<\/i>&#8220;) are not automatically added to the group\u00a0&#8220;<i>Print Operators<\/i>&#8220;. This makes sense in an environment where you don&#8217;t want Joe Public messing with printer settings. It makes less sense in a lab or production environment where the staff can be trusted with the printers.<\/p>\n<p>Fortunately, I found a simple solution <a href=\"https:\/\/discussions.apple.com\/message\/11936448?messageID=11936448\">here<\/a>:<\/p>\n<p>In Terminal.app, type the following:<\/p>\n<p><code>dseditgroup -o edit -u ADMINUSER -p -a USER -t user _lpadmin<\/code><\/p>\n<p>where ADMINUSER is the user name of an administrator and USER is the user name you want controlling the printer.<\/p>\n<p>You will be asked for the password of ADMINUSER and then USER is added to the &#8220;<i>_lpadmin<\/i>&#8221; group, solving the problem permanently.<\/p>\n<p><span style=\"background-color: yellow;\"><b>CAUTION<\/b><br \/>A word of advice to the wise: I do not know if adding a user to the group\u00a0&#8220;<i>_lpadmin<\/i>&#8221; has any side effects. The users of the machines I administer are considered trustworthy. The only reason they do not have administrative privileges is to protect the machines from unintended damage. So giving limited administrative privileges is not a problem. This may be different in your environment.<\/span><br \/><span><b style=\"background-color: yellow;\">Consider the implications carefully before making changes!<\/b><\/span><\/p>\n<p><b>Background Information<\/b><br \/>It appears that the problems observed are not uniform: some machines always show the problem, some not at all, and some only for some users.<\/p>\n<p>It looks like Apple changed the defaults some time during the life-cycle of Mac OS X 10.5 (I have been unable to ascertain when exactly). Users created before the change were all members of &#8220;<i>_lpadmin<\/i>&#8220;, users created later are not members.<\/p>\n<p>The best solution would be to tell CUPS (the printing system used in Mac OS X) to allow members of the group &#8220;<i>Staff<\/i>&#8221; to control the printer. To do so, the file\u00a0<i>\/etc\/cups\/cupsd.conf<\/i> section<\/p>\n<p><code><limit activate-printer=\"\" cups-accept-jobs=\"\" cups-reject-jobs=\"\" deactivate-printer=\"\" disable-printer=\"\" enable-printer=\"\" hold-new-jobs=\"\" pause-printer-after-current-job=\"\" pause-printer=\"\" promote-job=\"\" release-held-new-jobs=\"\" restart-printer=\"\" resume-printer=\"\" schedule-job-after=\"\" shutdown-printer=\"\" startup-printer=\"\">\u00a0 \u00a0 AuthType Default<br \/>\u00a0 \u00a0 Require user @AUTHKEY(system.print.operator) @admin @lpadmin<br \/>\u00a0 \u00a0 Order deny,allow<\/limit><\/code><\/p>\n<p>needs to be changed to something like<\/p>\n<p><code><limit activate-printer=\"\" cups-accept-jobs=\"\" cups-reject-jobs=\"\" deactivate-printer=\"\" disable-printer=\"\" enable-printer=\"\" hold-new-jobs=\"\" pause-printer-after-current-job=\"\" pause-printer=\"\" promote-job=\"\" release-held-new-jobs=\"\" restart-printer=\"\" resume-printer=\"\" schedule-job-after=\"\" shutdown-printer=\"\" startup-printer=\"\">\u00a0 \u00a0 AuthType Default<br \/>\u00a0 \u00a0 Require user @AUTHKEY(system.print.operator) @admin @lpadmin <b>@staff<\/b><br \/>\u00a0 \u00a0 Order deny,allow<\/limit><\/code><\/p>\n<p>I did <b>not<\/b> try this myself. If you do, you may find <a href=\"http:\/\/www.cups.org\/documentation.php\/doc-1.4\/ref-cupsd-conf.html#Limit\">cupsd.conf documentation<\/a> useful. I would appreciate a comment telling about your experiences. Good luck!<\/p>\n","protected":false},"excerpt":{"rendered":"<p>On Mac OS X 10.6 (Snow Leopard) a non-administrator user can not change all settings of the installed printers. This is really annoying when a printer error causes the print queue to go on hold: the user can not resume printing when the problem has been solved. Instead, a dialog pops up asking for the [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[463,464,183,188,461,465,467,462,466,192],"tags":[],"class_list":["post-810","post","type-post","status-publish","format-standard","hentry","category-10-6","category-cups","category-howto","category-mac-os-x-software","category-print-operators","category-printer","category-printing","category-snow-leopard","category-technical","category-tip"],"_links":{"self":[{"href":"https:\/\/doenges.com\/blog\/wp-json\/wp\/v2\/posts\/810","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/doenges.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/doenges.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/doenges.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/doenges.com\/blog\/wp-json\/wp\/v2\/comments?post=810"}],"version-history":[{"count":0,"href":"https:\/\/doenges.com\/blog\/wp-json\/wp\/v2\/posts\/810\/revisions"}],"wp:attachment":[{"href":"https:\/\/doenges.com\/blog\/wp-json\/wp\/v2\/media?parent=810"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/doenges.com\/blog\/wp-json\/wp\/v2\/categories?post=810"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/doenges.com\/blog\/wp-json\/wp\/v2\/tags?post=810"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}