[cups.development] IPP-Create/Print-Job unauthorized when auth-info-required

Tim Waugh twaugh at redhat.com
Wed Mar 4 07:34:11 PST 2009


I maintain an application (system-config-printer) which can perform 
"proxy authentication", that is to say: it watches the jobs queue, and 
when a job is stopped because the backend decides it needs 
authentication information, this application can provide the required 
authentication details and allow the job to resume.  It does this by 
displaying an authentication dialog to the user and then sending a 
CUPS-Authenticate-Job IPP request containing the information.

Everything works well when submitting a single job at a time and when 
the correct authentication details are supplied.  However when a job is 
stopped awaiting authentication details, no further jobs can be 
submitted without the authentication details being supplied there and 
then.  The IPP-Create-Job or IPP-Print-Job request made by whichever 
application is submitting the job must at this point supply auth-info.

What is the reason for this behaviour?  From my point of view it would 
be nicer if the job could be created as normal in this case.

Tim.
*/

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 251 bytes
Desc: OpenPGP digital signature
URL: <https://lists.cups.org/pipermail/cups/attachments/20090304/998da6f9/attachment.bin>


More information about the cups mailing list