8000 Windows 10 Basic Authentication · Issue #283 · istopwg/ippsample · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

Windows 10 Basic Authentication #283

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.

Sign up for GitHub

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

Jump to bottom
Open
sixteng opened this issue Nov 16, 2023 · 2 comments
Open

Windows 10 Basic Authentication #283

sixteng opened this issue Nov 16, 2023 · 2 comments
Assignees
@michaelrsweet
Labels
investigating platform-issue Issue is specific to an OS or desktop

Comments

@sixteng
Copy link
sixteng commented Nov 16, 2023 •
edited
Loading

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
@michaelrsweet michaelrsweet self-assigned this Nov 18, 2023
@michaelrsweet michaelrsweet added investigating platform-issue Issue is specific to an OS or desktop labels Nov 18, 2023
@michaelrsweet
Copy link
Contributor

I can't remember whether the current Win10 IPP class driver supports authentication, will confirm and update this bug.

@dkosovic
Copy link
dkosovic commented Dec 1, 2023

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@michaelrsweet michaelrsweet

Labels
investigating platform-issue Issue is specific to an OS or desktop
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@michaelrsweet @sixteng @dkosovic
0