[cups.general] [PyKota] Problems with Vista

[Jorge Granjal]

Hi, thank you for the prompt reply.

My username on the Pykota database is "jgranjal", same username I use 
on other network services. CUPS authenticates via PAM on Kerberos, so
I dont want to use my Windows logon name, just the username and password I
use on several network services.

That username is correctly authorized on pykota, I use that from XP desktops
without any problem.

On Vista, Windows sends the correct username when connecting to CUPS or when
I refresh the printer queue:

"Mar 22 10:37:59 ipp cupsd: pam_krb5[2189]: authentication succeeds for 
'jgranjal' (jgranjal at DEI.UC.PT)"

But when I submit a job it sends the username I use on the Windows desktop
(Windows logon name):

"Mar 22 10:39:38 ipp PyKota: (PID 5402) : jorge at minolta(31) => User 
jorge not registered in the PyKota system, applying default policy 
(DENY) for printer minolta
Mar 22 10:39:38 ipp PyKota: (PID 5402) : jorge at minolta(31) => User 
jorge doesn't have quota on printer minolta in the PyKota system, 
applying default policy (DENY)"

I guess CUPS extracts the username somehow from HTTP headers during the IPP
dialog and that will be the username passed do the PyKota filter.
What is strange is that this was never a problem with XP ou 2003.


Thank you again,

Jorge

Quoting Jerome Alet <alet at librelogiciel.com>:

> Hi,
>
> On Thu, Mar 22, 2007 at 11:01:21AM +0000, Jorge Granjal wrote:
>>
>> I'm using CUPS with XP, MacOSX and other clients successfully for years,
>> but I'm having a strange problem with the new Windows Vista.
>>
>> I have no problem defining the printer using a URL like
>> https://ourserver.ourdomain/printer/<printer>.
>>
>> On the properties of the printer, and selecting “Ports” and then
>> “Configure Port” I configure the username and password Windows should
>> use when connecting to the printer (selecting “Use the specified user
>> account”, just like on XP.
>>
>> My problem is that Windows uses that username to connect to CUPS, but
>> somehow uses the "Windows logon name" when printing. This is a problem
>> for me because I’m using Pykota with CUPS, and so pykota denies my
>> print job.
>
> I assume by this you mean Windows sends the fully qualified username
> (like 'DOMAIN/Username') and this causes a problem. If this is the
> case then set 'winbind_separator' to the appropriate value
> in pykota.conf and it should work as expected.
>
> You should also ensure that the username when stripped from the domain
> part is registered in PyKota's database and a print quota entry exists
> for this user on each printer you want to use this way (use the pkusers
> + edpykota command line tools to check and fix)
>
> Hoping this helps
>
> Jerome Alet
>
> _______________________________________________
> Technical Support : http://www.pykota.com/technical-support/
> Trouble Ticketing System : http://otrs.librelogiciel.com/otrs/customer.pl
> Download : http://www.pykota.com/software/pykota/download/tarballs
> pykota mailing list pykota at librelogiciel.com
> http://cgi.librelogiciel.com/mailman/listinfo/pykota
> DON'T POST IN HTML !
>



----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.