Job displays user as "Withheld"

[Logan Anteau]

> On Aug 12, 2011, at 8:30 AM, Logan Anteau wrote:
> > I'm trying to set up pykota with CUPS for print accounting. The pykota backend is failing because I believe it is not getting the job-originating-user-name from CUPS.
> >
> > When I look at the job details from the CUPS web interface I notice for user it says "Withheld" instead of my username (I expected user at REALM). So if it's withheld on the site I'm thinking its not telling pykota the user either. Why is this?
>
>
> Assuming that Pykota is using the username from the command-line, they will still be getting it.
>
> As for the "withheld" in the web interface, that is new security mojo in CUPS 1.5.0 that is controlled by the JobPrivateAccess and JobPrivateValues directives in each operation policy. Basically we now, by default, hide all "personal" information in jobs unless you are an admin or the owner of the job. You can disable this pretty easily to get the pre-1.5.0 behavior by replacing the existing lines in cupsd.conf with:
>
> 	JobPrivateAccess all
> 	JobPrivateValues none
>
> and then restarting cupsd (editing via the web interface will do this for you...)
>
> __________________________________________________
> Michael Sweet, Senior Printing System Engineer, PWG Chair
>

Thanks Michael for your quick response. This is the cause of my issue! Pykota uses a python IPP library to perform a IPP_GET_JOB_ATTRIBUTES and I believe the Get-Job-Attributes should return the job-originating-user-name, and with this security feature enabled it must not have been. Changing those lines as you described eliminated the error. This is something to be aware of for people wanting to use pykota. Unfortunately it seems to be the only full featured print accounting solution for CUPS. Thanks!