'Hold for Authentication' Error in Mac Print Queue
Last modified on 14 August 2020 04:35 PM
“Help! When printing from MacOS computers, sometimes we see the job stuck in the print queue with the message “Hold for Authentication.” What does this mean?”
Sometimes, when printing from a Mac, the job appears to pause in the print queue window with the message “Hold for Authentication”. This error indicates that the credentials that the Mac is providing are being rejected by the server it’s contacting. Select the option below that best describes what you’re seeing.
This message is often wholly unrelated to PaperCut. Usually, if you see this error, it is about the print queue’s OS-level authentication instead of PaperCut
Try the easy options first
Confirm correct setup of the print queue connection
Looking for an automatic option? Admins may be interested in our Print Deploy Solution!
Try a different driver
Force the Mac to request authentication
Check if you’re printing across subnets
As is the case without Mobility Print, the most common cause of the “Hold for Authentication” error is entering the username and password incorrectly. you should first attempt to re-enter the credentials by clicking the refresh button. If the problem was due to an incorrect username or password, the job should go through with the correct credentials after reentry.
Per-Job Authentication with Saved credentials
The message can also appear if the Mobility Print queue has Per-Job Authentication enabled and the user has peviously saved their credentials for printing in the Keychain. With credentials stored in the Keychain, the prompt for won’t pop up, but if opened, the print queue window shows “Hold for Authentication”. While annoying, this does prevent the more significant problem of a user accidentally saving their PaperCut credentials on a shared device.
A) Disable Per-Job Authentication - this will not be practical if your users share devices and you want to prompt for credentials with each Mobility Print job
B) Delete the credentials from KeyChain Access - Remove the credentials, cancel and retry the job to continue using Per-Job Authentication.
An apostrophe in the username
The apostrophe shortcoming is inherent to macOS whether the user authenticates with their apostrophe-enabled username on a print queue advertised from Mobility or a print queue published directly from an AirPrint-enabled printer. At the time of this writing, we have yet to determine whether this lapse is due to CUPS, macOS, both, or something else entirely.
A) Refresh and re-enter the same credentials - As a workaround, this allows the job to go through, but every print job sent will need this.
B) Turn on Username Aliasing - Enable username aliasing to add a username that excludes an apostrophe. Bear in mind, you will need to instruct your users to use this alternative username for Mobility Authentication.
A rogue Mobility server
In rare cases, an unintended Mobility Print server may make its way onto the network. This can happen when a user (we’ll call them Bob) is searching for the client-side applications, but stumbles upon the server installs for both PaperCut and Mobility Print. By accident, Bob has made their machine both a PaperCut Application Server, and a Mobility Print Server (this issue will not occur with Mobility Print without PaperCut installed to as it will not require authentication). Bob eventually adds the printer that’s been published on the true Mobility Print Server, and so it gets republished automatically by Bob’s rogue Mobility Print server.
The pickle in this case is that if another user has connected to the queues automatically published by Bob’s computer, any job sent to this rogue queue recieves “Hold for Authentication” on their macOS device or “Incorrect name or password on their iOS device.