Authorization in CUPS fails in google-chrome-stable
Hello, For reasons that do not matter right now I moved from FF to GCS as my default browser. A day ago I ran into printer problems that I usually addres by use of CUPS. Much to my dismay I could not do any aignificant work because of lack of authorization. Ordinarily a popup appears to let you enter credentials but it did not. After a day of hairpulling and spelunking the net i chanced on a message of some good soul who wrote that he had the same problem with chromium and that switching to a different browser solved it. Much to my surprise he was right. I went back to FF and there it was: the popup for my credentials. There ought to be a law that this should not happen. :) FF rocks! I wonder what particular bug triggers this behavior in GCS. But in case you run into something similar here's this one more thing to try. Regards, Jos -- Jos van Kan registered Linux user #152704
On 2022-03-18 17:10, Jos van Kan wrote:
Hello,
For reasons that do not matter right now I moved from FF to GCS as my default browser. A day ago I ran into printer problems that I usually addres by use of CUPS. Much to my dismay I could not do any aignificant work because of lack of authorization. Ordinarily a popup appears to let you enter credentials but it did not. After a day of hairpulling and spelunking the net i chanced on a message of some good soul who wrote that he had the same problem with chromium and that switching to a different browser solved it. Much to my surprise he was right. I went back to FF and there it was: the popup for my credentials.
There ought to be a law that this should not happen. :) FF rocks!
I wonder what particular bug triggers this behavior in GCS. But in case you run into something similar here's this one more thing to try.
I don't know, but I opened a page in Google Chrome right now and printed a page, no problem and no popup. Same behaviour as in FF. But when printing a second job, failed in mid-print, and when trying again it says that the printer failed and refuses. Says to check printer, but printer shows no error at all, nor cups, nor in the log. Went to FF, printed the same page with no trouble. -- Cheers / Saludos, Carlos E. R. (from 15.3 x86_64 at Telcontar)
On 2022-03-18 13:41:39 Carlos E. R. wrote:
|On 2022-03-18 17:10, Jos van Kan wrote: |> Hello, |> |> For reasons that do not matter right now I moved from FF to GCS as my |> default browser. A day ago I ran into printer problems that I usually |> addres by use of CUPS. Much to my dismay I could not do any aignificant |> work because of lack of authorization. Ordinarily a popup appears to |> let you enter credentials but it did not. After a day of hairpulling and |> spelunking the net i chanced on a message of some good soul who wrote |> that he had the same problem with chromium and that switching to a |> different browser solved it. Much to my surprise he was right. I went |> back to FF and there it was: the popup for my credentials. |> |> There ought to be a law that this should not happen. :) FF rocks! |> |> I wonder what particular bug triggers this behavior in GCS. But in case |> you run into something similar here's this one more thing to try. | |I don't know, but I opened a page in Google Chrome right now and printed |a page, no problem and no popup. Same behaviour as in FF. | |But when printing a second job, failed in mid-print, and when trying |again it says that the printer failed and refuses. Says to check |printer, but printer shows no error at all, nor cups, nor in the log. | |Went to FF, printed the same page with no trouble.
I believe that CUPS only asks for credentials when one goes into the Administration tools. Leslie --
On 2022-03-19 08:44, J Leslie Turriff wrote:
On 2022-03-18 13:41:39 Carlos E. R. wrote:
|On 2022-03-18 17:10, Jos van Kan wrote: |> Hello, |> |> For reasons that do not matter right now I moved from FF to GCS as my |> default browser. A day ago I ran into printer problems that I usually |> addres by use of CUPS. Much to my dismay I could not do any aignificant |> work because of lack of authorization. Ordinarily a popup appears to |> let you enter credentials but it did not. After a day of hairpulling and |> spelunking the net i chanced on a message of some good soul who wrote |> that he had the same problem with chromium and that switching to a |> different browser solved it. Much to my surprise he was right. I went |> back to FF and there it was: the popup for my credentials. |> |> There ought to be a law that this should not happen. :) FF rocks! |> |> I wonder what particular bug triggers this behavior in GCS. But in case |> you run into something similar here's this one more thing to try. | |I don't know, but I opened a page in Google Chrome right now and printed |a page, no problem and no popup. Same behaviour as in FF. | |But when printing a second job, failed in mid-print, and when trying |again it says that the printer failed and refuses. Says to check |printer, but printer shows no error at all, nor cups, nor in the log. | |Went to FF, printed the same page with no trouble.
I believe that CUPS only asks for credentials when one goes into the Administration tools.
I just started Chrome, went there, and got the login prompt, yes. -- Cheers / Saludos, Carlos E. R. (from 15.3 x86_64 at Telcontar)
On 19-03-2022 13:23, Per Jessen wrote:
Jos van Kan wrote:
I wonder what particular bug triggers this behavior in GCS. But in case you run into something similar here's this one more thing to try. By default CUPS uses a self-signed certificate, I think you only need to make GCS accept that.
OK, but how? It never asks for it, just says "unauthorized". -- Jos van Kan registered Linux user #152704
Jos van Kan wrote:
On 19-03-2022 13:23, Per Jessen wrote:
Jos van Kan wrote:
I wonder what particular bug triggers this behavior in GCS. But in case you run into something similar here's this one more thing to try. By default CUPS uses a self-signed certificate, I think you only need to make GCS accept that.
OK, but how? It never asks for it, just says "unauthorized".
I came across an article I think - https://www.pico.net/kb/how-do-you-get-chrome-to-accept-a-self-signed-certif... HTH, Per -- Per Jessen, Zürich (12.4°C)
On 2022-03-19 14:35, Jos van Kan wrote:
On 19-03-2022 13:23, Per Jessen wrote:
Jos van Kan wrote:
I wonder what particular bug triggers this behavior in GCS. But in case you run into something similar here's this one more thing to try. By default CUPS uses a self-signed certificate, I think you only need to make GCS accept that.
OK, but how? It never asks for it, just says "unauthorized".
Ah! I'm using http, not https. That's why I have no issue. http://localhost:631/printers/HP_Color_LaserJet_CP1515n I now tried on Chrome using https and indeed it says it is not safe. Click advanced, proceed to site (unsafe), and it works. I see Per has posted instructions on how to import the certificate. Wow, that's involved and "complicated", compared to FF. -- Cheers / Saludos, Carlos E. R. (from 15.3 x86_64 at Telcontar)
On 2022-03-19 09:15:18 Carlos E. R. wrote:
|Ah! I'm using http, not https. That's why I have no issue. | |http://localhost:631/printers/HP_Color_LaserJet_CP1515n | |I now tried on Chrome using https and indeed it says it is not safe. |Click advanced, proceed to site (unsafe), and it works.
One might think that for localhost, either http or https would be given the benefit of the doubt by one's browser, but I suppose whoever implemented the feature didn't think of this edge case. :-) Leslie --
participants (4)
-
Carlos E. R. -
J Leslie Turriff -
Jos van Kan -
Per Jessen