Comment 12 for bug 653132

Tim, one additional remark to above-mentioned problem:

There seems to be a CUPS connection with credentials for the main process of the s-c-p session and separate CUPS connections with their own credentials for asynchronous background processes like polling the list of detected printers.

If one logs in on the main CUPS connection first, for example by the first action being option default settings of an existing print queue, one can afterwards create a queue without getting asked for login/password again, but if the first action in the session is creating a queue, one gets asked at first before the list of detected devices gets shown and a second time at the end of the add-printer wizard when the queue gets created. But after that one can set option defaults of all existing printers without getting asked again.

In addition, when I have already created a printer or changed option settings of an existing printer and after that I try to remove a printer I get asked again, but starting the session with removing a printer allows changing option settings of another still existing printer without entering the credentials again. The login for deleting a printer also stays valid for the whole process of creating a new queue afterwards.

So prinmter deletion seems to have the most powerful authentication which stays valid for all the other actions, after that comes changing printer option settings which at least allows creating queues afterwards. The weakest seems to be listing detected printers as a new authentication for creating a queue is required.

Can you make this consistent, so that when the user logs in once so that he can do everything during the rest of the s-c-p session, independent of which he did first? Thanks.