Closed Bug 1333572 Opened 7 years ago Closed 7 years ago

Login Error received when printing to a MFP that requires authentication.

Categories

(Core :: Printing: Output, defect)

50 Branch
Unspecified
macOS
defect
Not set
normal

Tracking

()

RESOLVED WORKSFORME

People

(Reporter: drew, Unassigned, NeedInfo)

Details

(Keywords: regressionwindow-wanted)

User Agent: Mozilla/5.0 (Windows NT 10.0; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/55.0.2883.87 Safari/537.36

Steps to reproduce:

1.	Enable User Authentication on my Konica Minolta bizhub C308 multi-function printer.  Menu>Utility>Administrator Settings>User Authentication/Account Track>General Settings>User Authentication> Authenticate on MFP> Touch OK to confirm settings
2.	Create a user on the bizhub C308 Menu>Utility>Administrator Settings>User Authentication/Account Track> User Registration>Select empty user box>Edit>Enter desired user name and password.
3.	Install Up-to-date driver from www.konicaminolta.us website (6.1.1 Released 10/5/16) on Mac
4.	From OS X open System Preferences and click Print & Scan.  Click the + under the printer list to add a printer.  Select printer from list in Default tab if bonjour activated on the MFP, if not add by IP from the IP tab.  In the Use drop down select the proper bizhub C308 print driver that was previously installed (AIRPRINT WILL NOT WORK AT ALL WITH AUTHENTICATION).  Click Add
5.	Send a test print by opening a PDF document in acrobat or preview.  Click File>Print.  In the center drop down (labeled “Preview” in preview) select “Output Method”.  Check the “User Authentication check box and you will be prompted for your user name and password that was previously entered on the MFP in step 2.  Be sure Recipient User is checked and not public user.  Click OK and then Print.  Expected Results: The job should process, authenticate and print.  Actual Results: Job processes, authenticates and prints.
6.	Open Firefox 50 or 51.  Navigate to any webpage.  Follow the same steps to print as in step 5.  The job will process on the computer, the MFP data light will blink for a few seconds then the job will fail.  Expected Results: The Job should process, authenticate and print.  Actual Results: the job processes on the workstation but fails with a “Login Error” once received by the MFP.
7.	From the bizhub MFP, touch Job List, touch the center tab labeled Jobs.  The first job should be the failed print job.  Highlight it and touch details.  The error details will show “Login Error”
I and Konica Minolta have been able to reproduce this error consistently across multiple offices, computers, and profiles.  It only occurs on OS X running FireFox 50+.  Windows and older versions on Firefox work without error.  It is consistent and I don’t believe it is limited to just the Konica Minolta brand of MFP.  I found a similar bug report from a couple weeks ago using a Savin MFP (1330379).  Below is what was received after Konica Minolta developers tested the failure.
We have confirmed that this symptom occurs because of the malfunction of Firefox application,regardless to PS driver.
After a deep investigation, we realize that Firefox(Version50.0) does not pass the driver settings to the spooler.
Therefore,those neccessary PJL commands are not written in the print data, causing "Login Error" on MFP during user authentication printing.

From the capture data retrieved from MFP, we know the following information is not included in the print data sent by the driver.
@PJL SET USERNAME = "ops"
@PJL SET HOLD = OFF
@PJL SET BOXHOLDTYPE = PRIVATE
@PJL SET KMUSERNAME = "konica"
@PJL SET KMUSERKEY2 = "2F575AB33A772D02D189CFBDE48D16F1"
@PJL SET KMCERTSERVTYPE = NONE
@PJL SET KMCERTSIMPLEAUTHREQ = OFF
@PJL SET CHAPTERMODE = OFF
@PJL SET IMAGESHIFT = OFF
@PJL SET EDGEMATCHING = FINISH
@PJL SET OUTBIN = DEFAULT
@PJL SET JIMONMODE = OFF
@PJL SET DTSTPMODE = OFF
@PJL SET PAGESTAMP = "NONE,1,1"
@PJL SET HFSTPMODE = OFF
@PJL SET PLANESINUSE = 3

This symptom does not occur if Firefox like Version 48.0,38.0,30.0 are used because these versions of the Firefox pass the driver settings to the spooler.

As we conclude this symptom is related to Firefox itself, it is difficult to solve this symptom by modifying the driver.
As a workaround, please use other web browser such as Safari if you wish to use user authentication to make a print.
I did test with version 51 today at about 3:00pm and the problem continues to occur.




Actual results:

Failure to print from Firefox in any form.  MFP gives a "Login Error" on all received print jobs received from Firefox 50+.  All other browsers (chrome/safari) and applications (preview/adobe) print as expected.


Expected results:

File should have printed at the copier and the copier logs authentication information for tracking purposes.
It appears to be a regression in FF50+.

Could you install the tool mozegression (http://mozilla.github.io/mozregression/) to narrow down a regression range.
Run the command "mozregression --good=49" then copy here the final pushlog.
Component: Untriaged → Printing: Output
Flags: needinfo?(drew)
OS: Unspecified → Mac OS X
Product: Firefox → Core
Hello,
I've had some problems getting mozregression working.  I run the command mozregression --good 48 --bad 50 (when running just mozregression --good=49 I get an error "no 'bad' option specified").  It downloads and says it's launching 49.0a1 but the nightly doesn't open.  If i say it's "good" it downloads and actually launches 51.0a1.  I can test 51.0a1 and it fails.  Then no other nightly will load to be tested.

On a side note I downloaded Nightly 54.0a1 this morning and tested it.  All seems to be back to working properly on this build.

Do you have any suggestions on getting mozregression working properly or what i'm doing wrong?  Since the problem seems to be corrected now I would assume that the next release will be corrected.
Given comment 2 "Nightly 54.0a1 is working". I will close this issue as works for me. If this issue persists, please reopen.
Status: UNCONFIRMED → RESOLVED
Closed: 7 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.