You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When a job is submitted for a printer with an ipp://... URI, and the IPP backend cannot proceed because the remote IPP instance requires auth-info, the job cannot be authenticated.
Details:
Set up a CUPS server on the network and share a queue using CUPS Browsing. Add this policy fragment:
AuthType Basic
Require valid-user
so that authentication is required before a job can be submitted.
Configure a CUPS 1.3.6 client to discover browsed printers using CUPS Browsing
On this client machine, submit a print job to the browsed queue. The job will stop because authentication is required.
Send a CUPS-Authenticate-Job IPP request for that job to the client, with auto-info set to the correct values.
The job restarts but stops again as in step 3. The authentication details were not given to the CUPS server.
There are two things wrong:
A. The IPP backend does not try to send authentication details unless it is running as root, and the scheduler does not run it as root even if it sets authentication details in the environment.
B. The IPP backend is looking in the environment for AUTH_USERNAME and AUTH_PASSWORD, but the scheduler sets CUPSD_AUTH_USERNAME and CUPSD_AUTH_PASSWORD.
Attached is a fix for the second problem.
The text was updated successfully, but these errors were encountered:
diff -up cups-1.3.6/backend/ipp.c~ cups-1.3.6/backend/ipp.c
--- cups-1.3.6/backend/ipp.c~ 2008-03-05 15:40:11.000000000 +0000
+++ cups-1.3.6/backend/ipp.c 2008-03-12 12:55:20.000000000 +0000
@@ -544,12 +544,12 @@ main(int argc, /* I - Number of comm
* Try loading authentication information from the environment.
*/
Version: 1.3.6
CUPS.org User: twaugh.redhat
When a job is submitted for a printer with an ipp://... URI, and the IPP backend cannot proceed because the remote IPP instance requires auth-info, the job cannot be authenticated.
Details:
so that authentication is required before a job can be submitted.
There are two things wrong:
A. The IPP backend does not try to send authentication details unless it is running as root, and the scheduler does not run it as root even if it sets authentication details in the environment.
B. The IPP backend is looking in the environment for AUTH_USERNAME and AUTH_PASSWORD, but the scheduler sets CUPSD_AUTH_USERNAME and CUPSD_AUTH_PASSWORD.
Attached is a fix for the second problem.
The text was updated successfully, but these errors were encountered: