Authentication to CUPS from kprinter

[Kurt Pfeifle]

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

[....]
> > Please do also post the complete contents of
> >
> >   $(kde-config --localprefix)/share/config/kdeprintrc
> >   $(kde-config --localprefix)/share/config/kprinterrc
> >   /etc/cups/client.conf    # leave out the comment lines
> >   $HOME/.cupsrc            # leave out the comment lines
> >   $HOME/.cups/client.conf  # leave out the comment lines
> >
> > (Some of these files may not exist on your system)
> >   
> ---------------
> 
> UserA at ClientA:/etc/ssl/certs> cat /home/UserA/.kde/share/config/kdeprintrc
> [$Version]
> update_info=kdeprintrc.upd:kde-3.1-toolbar
> 
> [CUPS]
> Host=ServerA
> InstallDir=
> Login=UserA
> Port=631

Well, this last line tells kprinter to access the CUPS server via 
port 631, and *not* via 443 as you stated....

> SavePassword=false

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

Also, please check your server's cupsd.conf. Do you have 2 different 
"Listen" statements included there, where one is naming a Unix Domain 
Socket (file) [domain socket support was newly introduced with CUPS 
1.2.0], the other one a TCP/IP socket. Try to move the domain socket 
*below* all other "Listen" or "Port" statements.

So what's the output of

  grep -v ^# /etc/cups/cupsd.conf | grep -v ^$

when run on the CUPS server?


I'm sorry, I can't even try to reproduce your problem; I've currently
no Linux or KDE system I could use for this (notebook was stolen,
and a lottery win for me is just not happening) -- so what I say is
just from my fading memory....

Cheers,
Kurt