Policy with multiple cases for different clients

voravit voravit at kth.se
Fri Jan 25 12:06:10 PST 2008


Well, it actually said in CUPS's Managing Operation Policies as well as in cupsd.conf man page that Satisfy directive can be used.

Anyhow, I did try to force everyone to authenticate instead. But this work only on windows clients when I add printer with https://ip:631/...  URI format but it doesn't work with my linux clients.

My linux client detected the printer automatically but when I tried to print, I've never got a pop up for username/password. I got this debug message in CUPS print server:

cupsdCallPamAuthHelper: authentication helper returned with 1
cupsdAuthorize: PAM authentication helper: wrong credentials
cupsdSendError: 11 code=401 (Unauthorized)

How can I force my linux clients (using IPP protocol) to be authenticated? Or do I really need to set up PAM for CUPS to authenticate?

Best regards,
Voravit T.



> voravit wrote:
> > Well, I actually want to allow one network to print and other networks need to be authenticated first. This should be possible if I use the following configuration, right?
> >
> >   <Limit All>
> >     Order allow,deny
> >     Allow from 192.168.0.0/24
> >     Require user test  #or Require valid-user
> >     Satisfy any
> >   </Limit>
> >
> > However, it didn't work for me. My clients were never authenticated (never been prompt for username/password). I can see in the log saying "No authentication data provided". How do I force CUPS to prompt for authentication?
>
> Put the address restrictions in the Locations - IIRC the satisfy stuff
> is currently only supported in Locations, not Policies...
>
> --
> ______________________________________________________________________
> Michael R Sweet                        Senior Printing System Engineer
>





More information about the cups mailing list