Mailinglist Archive: opensuse-bugs (4060 mails)

[bugzilla_noreply@xxxxxxxxxx]

https://bugzilla.novell.com/show_bug.cgi?id=661845

https://bugzilla.novell.com/show_bug.cgi?id=661845#c2


Lars Müller <lmuelle@xxxxxxxxxx> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEEDINFO                    |NEW
       InfoProvider|samba-maintainers@xxxxxxx   |

--- Comment #2 from Lars Müller <lmuelle@xxxxxxxxxx> 2011-01-04 12:02:56 CET ---
As soon as you have a valid kerberos ticket granting ticket (TGT) you no longer
need a password to authenticate.  _If_ the targeted service is kerberized.

Instead of adding any additional question like "Do you like to install the
samba-krb-printing package?" to the YaST printing dialog we should consider to
add a recommenrds samba-krb-printing to the samba-winbind package.

The TGT you get with the initial authentication via the display manager.  We've
tested this with the one from Gnome and KDE.  Therefore usually a further input
of a password isn't required.

get_printing_ticket uses the username as offered as second argument after the
DEVICE_URI

For testing you have to prompt for a username and password while in this
particular case the username is a construct of
<DOMAIN_NAME><WINBIND_SEPARATOR><USER_NAME>  The most common case for the
winbind separator is the \ char.  I would keep this as simple as possible and
therefore only offer a username and password inout field.  In the documentation
to the username field we might offer an example like EXAMPLEDOM\joe

I count the get_printing_ticket hack a superset but haven't tested this.

The drawbacks are: This is hack and it's not upstream (well, this might
change).  As soon as the printer destination isn't the next hop (think of
chained print servers) a forward able ticket would be required.

-- 
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.