<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=iso-8859-1">
<META content="MSHTML 6.00.2800.1400" name=GENERATOR></HEAD>
<BODY style="MARGIN: 4px 4px 1px; FONT: 10pt Tahoma">
<DIV>I've been having difficulties printing to a restricted ipp device. Here is the configuration.</DIV>
<DIV> </DIV>
<DIV>Created a printer (device type ipp) on cups server. This server is configured to broadcast printer on my subnet and for this particular device I have added the following to cupsd.conf</DIV>
<DIV> <Location /printers/HP4500></DIV>
<DIV> AuthType Digest #have tried AuthType Basic as well</DIV>
<DIV> </Location></DIV>
<DIV>Restarted cupsd and my client machine receives the printer. Now if I attempt to print, using for example kdelib's cupsdoprint, I receive a dialog asking for credentials. I provide valid credentials for the target server however the job never leaves the local spooler. I found that the ipp backend spawned by the local spooler is attempting to "get-printer-attributes" from the server, which responds 401 Not Authorized. The ipp backend then checks for ipp_status returned from the server and in the case of Not Authorized will sleep for 10 seconds and then return to the beginning of a loop to attempt the request again. I see that the ipp backed expects credentials to be included in the URI passed in argv[0]. The username:password provided to the "Authorization Dialog" never make it to argv[0] URI passed to the ipp backend. The backend will remain in this loop until the job is canceled.</DIV>
<DIV> </DIV>
<DIV>I can successfully print to a restricted device if I manually install the device on the client, i.e. add printer through the web interface/command line tools, and edit the client's cupsd.conf with identical location specified above. In this case the local spooler (cupsd) verifies the credentials and the ipp backend send the job directly to the device.</DIV>
<DIV> </DIV>
<DIV>Is there something I'm missing when the remote device requires authentication? How does the local spooler know the remote device is restricted and thus pass the required credentials to the ipp backend that will communicate with the device?</DIV>
<DIV> </DIV>
<DIV>cups 1.1.20</DIV>
<DIV>SuSE 9.1</DIV>
<DIV>kdelibs3 3.2.1</DIV>
<DIV> </DIV>
<DIV>Thanks in advance.</DIV>
<DIV>Jim</DIV>
<DIV> </DIV></BODY></HTML>