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
{{ message }}
This repository was archived by the owner on Mar 10, 2026. It is now read-only.
Repository navigation
This repository was archived by the owner on Mar 10, 2026. It is now read-only.
web interface doesn't show printers with allowed-users set #1700
Because the web interface CGI sets the username to 'guest', printers with 'requesting-user-name-allowed' set (and not containing 'guest') do not appear in the list at http://localhost:631/printers.
Can this be intentional? I couldn't see how to influence the 'REMOTE_USER' variable that the CGI uses.
This is really intentional - in the 1.1.x days we had many customers that complained that users saw printers they couldn't access. The command-line programs similarly limit their list of printers...
What you need to do in this situation is to add a Limit for GET requests so that you have the real user name, e.g.:
Alternately you can file a RFE to add a configuration option for this (e.g. /etc/cups/cgi.conf and "DefaultUser foo") so that the old behavior can be restored without requiring a username and password.
It makes perfect sense for cupsGetDests() to restrict the list of printers to those available to the current user. cupsGetDests() is used by client applications.
But for the web administration interface I don't understand why it needs to be restricted.
After all, I expect to be able to modify the list of allowed users for any given printer -- especially those with an existing allowed users list!
Well, the web interface is not just for administration - many people use it for monitoring and job control, too.
Anyways, looking through my notes, it appears that all of the customers using this feature have authentication enabled, so it should be sufficient to simply omit the requesting-user-name attribute when REMOTE_HOST is not set. That will restore the previous behavior with the default configuration.
Activity
michaelrsweet commentedon May 17, 2006
CUPS.org User: mike
This is really intentional - in the 1.1.x days we had many customers that complained that users saw printers they couldn't access. The command-line programs similarly limit their list of printers...
What you need to do in this situation is to add a Limit for GET requests so that you have the real user name, e.g.:
Alternately you can file a RFE to add a configuration option for this (e.g. /etc/cups/cgi.conf and "DefaultUser foo") so that the old behavior can be restored without requiring a username and password.
michaelrsweet commentedon May 17, 2006
CUPS.org User: twaugh.redhat
It makes perfect sense for cupsGetDests() to restrict the list of printers to those available to the current user. cupsGetDests() is used by client applications.
But for the web administration interface I don't understand why it needs to be restricted.
After all, I expect to be able to modify the list of allowed users for any given printer -- especially those with an existing allowed users list!
michaelrsweet commentedon May 17, 2006
CUPS.org User: mike
Well, the web interface is not just for administration - many people use it for monitoring and job control, too.
Anyways, looking through my notes, it appears that all of the customers using this feature have authentication enabled, so it should be sufficient to simply omit the requesting-user-name attribute when REMOTE_HOST is not set. That will restore the previous behavior with the default configuration.
michaelrsweet commentedon May 21, 2006
CUPS.org User: mike
Fixed in Subversion repository.