Authentication to CUPS from kprinter

[Kurt Pfeifle]

On Tuesday 12 September 2006 18:19, Helge Hansemann wrote:
> Kurt Pfeifle wrote:
> > On Tuesday 12 September 2006 11:29, Helge Hansemann wrote:
> >   
> >> Kurt Pfeifle wrote:
> >>     
> >>> On Tuesday 12 September 2006 08:42, Helge Hansemann wrote:
> >>>       
> >
> >   
> >>> Which version of KDE is that?
> >>>   
> >>>       
> >> KDE-Version:  3.4.2 Level "b"
> >>     
> >
> > KDE 3.4.2 may have problems authenticating to a CUPS 1.2.x server,
> > to be honest.
> >
> > Just look at
> >
> >     http://bugs.kde.org/show_bug.cgi?id=115891
> >     http://bugs.kde.org/show_bug.cgi?id=124157
> >
> > and a few other KDEPrint problems that popped up when CUPS 1.2.0 was 
> > released:
> >
> >     http://www.kdedevelopers.org/node/1901
> >
> > [....]
> >   
> All right, I will have a closer look to them tomorrow.

[....]
> > You should try with a setup that saves the password. Access it via the
> > "System Options"-button of kprinter. That will lead to include the 
> > following statements in kdeprintrc:
> >
> >   [CUPS]
> >   Host=ServerA
> >   InstallDir=
> >   Login=UserA
> >   Port=631
> >   Password=[whatever_will_be_written_here_(encrypted)]
> >   SavePassword=false
> >
> >   
> I did, and the result looks like this:
> The Password Line is not existent, and, if I put one by hand, it is
> deleted after closing kprinter - maybe a hint?

kprinter writes it upon closing to save its last configuration. Note,
I didn't suggest to edit it manually (you *could* do, but kprinter 
should not be opened at that moment), but I said:

  "Access it via the 'System 
   Options'-button of kprinter."

Sorry if I didnt make it clear enough.

[....]
> > So what's the output of
> >
> >   grep -v ^# /etc/cups/cupsd.conf | grep -v ^$
> >
> >   
> Here it comes, I deleted the Port line "Port 631", which was before the
> SSLPort line - (results in a failing cancel command on the command line,
> cause Port 631 is not accessible)
> 
> (By the way, if I comment out the two authentication lines in the
> "cancel-Job" policy section, it works)
> 
> (in my system its in /usr/local/cups/etc/cups/cupsd.conf.default)
> 
> LogLevel debug2
> SystemGroup sys root
> SSLPort 443
> Browsing On

So there seems no "Listen" or "Port" line included in your cupsd.conf.
Which means, CUPS will simply use the compiled-in defaults. BTW,
"SSLPort 443" has a slightly different meaning, which you can read up
about in the documentation:

   http://localhost:631/help/ref-cupsd-conf.html?TOPIC=References&QUERY=#SSLPort

OK, let's try one more thing, so you have the order of "Listen" lines
so that the domain socket is named last:

 LogLevel debug
 SystemGroup sys root
 Listen *:631
 Listen /usr/local/cups/etc/cups/cups.sock
 Browsing On

(Which means: 
 1. go back to "LogLevel debug" for now
 2. Do *not* explicitely specify an SSLPort
 3. Put the domain socket *after* the network socket
 4. Take care to have not an additional "Port" or "Listen" line that
    uses network sockets)

Shut down and start cupsd again after changing the cupsd.conf.

Note, that my suggested path for the domain socket is of course not
LSB compliant, but that does not matter for now. I don't know what 
your compiled-in default is for that, but if cupsd.conf does specify
a path+name, cupsd upon startup will create it automatically if it 
does not yet exist.

Cheers,
Kurt