Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

"requesting-user-name" and "$3 in argv" don't match in Samba/ADS/winbindd environment #465

michaelrsweet opened this issue Dec 6, 2003 · 1 comment


Copy link

@michaelrsweet michaelrsweet commented Dec 6, 2003

Version: 1.1.17 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 "" and "" 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...)

Copy link
Contributor Author

@michaelrsweet michaelrsweet commented Dec 6, 2003 User: mike

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
1 participant