Open sixteng opened 9 months ago
I can't remember whether the current Win10 IPP class driver supports authentication, will confirm and update this bug.
With the driverless Windows IPP inbox class driver and CUPS 2.4.7 authenticated queues, I observed using Wireshark that uri-authentication-supported
is never requested, nor does it respond accordingly to the HTTP 401 unauthorized response, it just keeps trying the IPP Validate-Job
operation (every 5 seconds).
Also annoyingly, requesting-user-name
is often not correct, initially it provides DOMAIN\username , but after the Win11 PC is rebooted, it switches to using a DOMAIN\computername$ account, but with no rhyme or reason it occasionally switches back to DOMAIN\username.
I wish Microsoft Universal Print client side could be reconfigured to use OAuth2 with CUPS 2.5.
We are attempting to add basic authentication to the ipp-everywhere-pdf server, but are unable to print from Windows 10
When attempting to print an pdf to the printer using windows 10, ipp 2.0 the print job gets marked with error in the queue, but no message or authentication request to enter credentials is show on the client side
We are running the ippserver on an Ubuntu Server using docker Only server we are running is the ipp-everywhere-pdf printer Authentication seems to be working if we add it from an Ubuntu / Linux machine Uri ipp://ippserver.local:8000/ipp/print/ipp-everywhere-pdf
Config has
AuthTestPassword test123 Authentication Yes AuthType Basic
I have attached a log from the ippserver
What is causing this issue ? Dose windows 10 not support Basic Auth
Server is running Ubuntu Client ( trying to print ): Windows 10 22H2 19045.3693
logs.log