Issue metadata
Sign in to add a comment
|
Unauthorized on CUPS admin pages
Reported by
t...@alexatilbrook.org,
Apr 30 2018
|
||||||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/66.0.3359.139 Safari/537.36 Steps to reproduce the problem: 1. On Ubuntu, go to http://localhost:631 2. Do anything requiring admin privilege. 3. The following message appears: "Unauthorized Enter your username and password or the root username and password to access this page. If you are using Kerberos authentication, make sure you have a valid Kerberos ticket." Screenshot: http://filerepo.alexatilbrook.org/Stuff/CUPS_Unauthorized.png What is the expected behavior? An HTTP basic auth dialog should appear. What went wrong? This is broken. Has Google been violating established RFC's for HTTP basic auth? Did this work before? Yes 64.0(?) Chrome version: 66.0.3359.139 Channel: stable OS Version: Flash Version: It works in Firefox, and other browsers. Just not Chrome or Chromium.
,
May 1 2018
,
May 2 2018
Uh... what triage info is needed, Susan? From Manjaro's forum: https://forum.manjaro.org/t/latest-chrome-unauthorized-to-alter-cups/45286 Ubuntu's: https://ubuntuforums.org/showthread.php?t=2388741 This is a CHROME issue. What part of it works in Firefox is misunderstood?
,
May 2 2018
Thanks for filing the issue! Tried checking the issue on reported chrome version 66.0.3359.139 using Ubuntu 14.04 with the below mentioned steps. 1. Launched Chrome 2. Navigated to http://localhost:631 3. Clicked on menu icons We didn't observe any message being shown, attaching the screen cast of the same. Similar behaviour is seen in firefox and M64. @Reporter: Could you please have a look at the screen cast and let us know if we have missed anything. As we are not very clear about point no.2 in comment#0 it would be highly helpful if elaborated on it. Any further inputs from your end may be helpful.
,
May 2 2018
,
May 2 2018
,
May 4 2018
I was going to look at it, but I can't seem to log into local CUPS with Firefox either, so will have to leave this to someone else. Nothing looked particularly suspicious in netlog or trying to wireshark it, either.
,
May 21 2018
@Reporter: Are you able to reproduce this in an incognito window or a fresh install? Otherwise, please attach a NetLog per these instructions: https://dev.chromium.org/for-testers/providing-network-details That will help see whether Chrome is correctly receiving the expected auth headers.
,
May 30 2018
[tiff]: Could you pleas respond to comment #8?
,
Jun 20 2018
Poking through some of the referenced threads, it seems the issue was that CUPS was sending multiple challenges in a single WWW-Authenticate header, which chrome doesn't support. Though without a netlog or update from the reporter it's hard to say for sure if it was the same issue. A workaround was committed to CUPS, so you could try to update CUPS if you're still seeing the problem. (https://github.com/apple/cups/issues/5289) There was an old bug about that issue which got auto-archived: issue 103220
,
Jul 9
Arching out this issue, as no responses from Comments #8, #9 and Comment #10. If there are further details, we're happy to investigate further if you file a new bug. |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by t...@alexatilbrook.org
, Apr 30 2018115 KB
115 KB View Download