You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is in continuation of STR #460.... (Sorry, I couldn't find a link to add more comments of mine -- probably because you closed STR #460 already.)
You argued: "please report this to the SAMBA folks; the domain part of the username shouldn't be passed in with the job..."
I'm not so sure about it. In a "SSO" (Single Sign On) environment the domain part IS part of the username. Users "smith" and "root" from
domains "kpfeifle.org" and "sweet.net" are two distinct users. And both
may be able to sign on to Unix resources and Windows resources if the
system is set up to support both (through the "winbindd"/LDAP/whatever setup.
I believe it is very important for CUPS to support this concept in the newer versions.
The "fix" might be easy enough. In any case it doesn't seem to be correct to translate the "DOMAIN\username" into 2 different representations ('DOMAIN_username' and 'DOMAIN') from what I can see in the error_log. (No idea where in the CUPS source code this happens...)
The text was updated successfully, but these errors were encountered:
Since SAMBA passes in the username, the fix has to happen there. If we change the username handling in CUPS to workaround the SAMBA issue, then there will be side-effects that could break other uses!
Since the Windows IPP and LPD code sends the username without the domain, the SAMBA code should be changed to drop the domain.
Version: 1.1.17
CUPS.org User: pipitas
This is in continuation of STR #460.... (Sorry, I couldn't find a link to add more comments of mine -- probably because you closed STR #460 already.)
You argued: "please report this to the SAMBA folks; the domain part of the username shouldn't be passed in with the job..."
I'm not so sure about it. In a "SSO" (Single Sign On) environment the domain part IS part of the username. Users "smith" and "root" from
domains "kpfeifle.org" and "sweet.net" are two distinct users. And both
may be able to sign on to Unix resources and Windows resources if the
system is set up to support both (through the "winbindd"/LDAP/whatever setup.
I believe it is very important for CUPS to support this concept in the newer versions.
The "fix" might be easy enough. In any case it doesn't seem to be correct to translate the "DOMAIN\username" into 2 different representations ('DOMAIN_username' and 'DOMAIN') from what I can see in the error_log. (No idea where in the CUPS source code this happens...)
The text was updated successfully, but these errors were encountered: