Bug 44085 - pdfPrinterShare not accessible for users with capital letters
pdfPrinterShare not accessible for users with capital letters
Status: RESOLVED WONTFIX
Product: UCS
Classification: Unclassified
Component: Printserver
UCS 4.2
Other Linux
: P5 normal (vote)
: ---
Assigned To: UCS maintainers
UCS maintainers
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2017-03-27 14:32 CEST by Felix Botner
Modified: 2020-07-03 20:56 CEST (History)
2 users (show)

See Also:
What kind of report is it?: Bug Report
What type of bug is this?: 4: Minor Usability: Impairs usability in secondary scenarios
Who will be affected by this bug?: 1: Will affect a very few installed domains
How will those affected feel about the bug?: 2: A Pain – users won’t like this once they notice it
User Pain: 0.046
Enterprise Customer affected?:
School Customer affected?:
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number:
Bug group (optional):
Max CVSS v3 score:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Felix Botner univentionstaff 2017-03-27 14:32:02 CEST
univention-printserver-pdf creates the following samba share

more /etc/samba/shares.conf.d/pdfPrinterShare 
[pdfPrinterShare]
path = /var/spool/cups-pdf/%U

But the logon with a user with capital letters in the username fails:

->  smbclient -UAdministrator%univention //10.200.7.53/pdfPrinterShare
Domain=[FOUR] OS=[] Server=[]
tree connect failed: NT_STATUS_BAD_NETWORK_NAME

[2017/03/27 14:28:54.300999,  0] ../source3/smbd/service.c:755(make_connection_snum)
  canonicalize_connect_path failed for service pdfPrinterShare, path /var/spool/cups-pdf/administrator

Seems that samba uses the lowercase username.

Workaround: 

Use "%u" (path = /var/spool/cups-pdf/%u) in the share path, man smb.conf says


       %U
           session username (the username that the client wanted, not 
           necessarily the same as the one they got).

       %u
           username of the current service, if any.
Comment 1 Ingo Steuwer univentionstaff 2020-07-03 20:56:41 CEST
This issue has been filed against UCS 4.2.

UCS 4.2 is out of maintenance and many UCS components have changed in later releases. Thus, this issue is now being closed.

If this issue still occurs in newer UCS versions, please use "Clone this bug" or reopen it and update the UCS version. In this case please provide detailed information on how this issue is affecting you.