Comment 36 for bug 283811

Reading http://www.cups.org/str.php?L2268+P0+S0+C0+I0+E0+M20+Q2268 (The wish-bug report that have given life to auth-info-required attribute, implemented by the bug reporter himself, Mike) is enlightening.

It would probably be even more if I knew a bit more about CUPS.

After reading it, I understand a bit the fact that it is normal that the line:
auth-info-required username,password
keeps 'creeping in' (English is not my first language, excuse if the expression is wrong) in printers.conf file.

<<
BACKENDS

Backends will continue to get the authentication information from the cache file (aNNNNN in the spool directory, where NNNNN is the job ID). The format of this file is one authentication value per line, with each value Base64-encoded.

When the authentication fails, backends can send an "ATTR: auth-info-required=..." message to stderr to reconfigure the auth-info-required attribute on the queue, and then exit with code 2 to indicate that authentication is required.
>>

and the auth-info-required is then save 'normally' when the printers.conf file is saved.

This suggest than rather than remove that line, it would be better to change it to become:
auth-info-required none
that would indicate that the remote system where the printer is, does not request any authorization.

Also, since Gnome seems unable to request a username and password yet, it would be good to also add a line:
auth-info-supported none
to indicate that the local system have no idea how to deal with authorization.
Or does it knows how to deal with 'domain' authorization?