[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#712872: cups: [RFE] Modifying authentication data for a job in the queue



Didier, Sam,

On 2013-06-20, at 8:41 AM, Didier 'OdyX' Raboud <odyx@debian.org> wrote:

> Control: tags -1 +upstream
> 
> Hi Sam, and thanks for your bugreport,
> 
> I'm hereby CC'ing Michael Sweet, Cups upstream author.
> 
> Le jeudi, 20 juin 2013 13.59:37, Sam Morris a écrit :
>> Some programs (such as Libreoffice) do not provide a way to specify a
>> username and password when printing to a printer that has
>> "AuthInfoRequired username,password" in its printers.conf entry.
>> 
>> A job created by such a program will sit in the queue until an
>> administrator removes it.
>> 
>> I'd like a way for the administrator to specify authentication values
>> for such a job that has been created without them. Something like:
>> 
>> 	# lpmodify -o username=foo,password 7
>> 	Enter value for 'password': *******
>> 
>> Here the given value was used for username, and since no password was
>> specified it was prompted so that it is not visible in the process's
>> command line arguments, nor is it recorded in the user's shell
>> history.
> 
> So you are asking for a feature to modify cups jobs to add missing 
> credentials to them so that they can succeed on restricted printers, 
> right?


CUPS supports (since 1.4 I think) the auth-info-required printer attribute ("username,password" for your usage) and the auth-info operation attribute (two strings containing the required auth info). The auth-info can be specified both at job creation and later using the CUPS-Authenticate-Job operation.  Jobs that require authentication are held with the auth-info-required reason.  And IIRC Tim Waugh's printer monitor for GNOME already supports doing the authentication when it sees this.

Right now there is no CUPS command to re-authenticate a job from the command-line, but I could look at adding it to the lp command's "-i" option...

_________________________________________________________
Michael Sweet, Senior Printing System Engineer, PWG Chair


Reply to: