
PaperCut NG/MF uses the job’s source IP address to determine the PaperCut NG/MF popup client it should contact for authentication. The print job arrives in the print queue and because of the unauthenticated protocol, the username cannot be trusted. The user initiates a print job to a server-hosted, PaperCut NG/MF-managed, queue (printer) via unauthenticated print protocol. Popup authentication matches the source IP address of the print job with the user confirmed to be operating from the popup client IP address. Common examples include:Īll users log in with a common generic username and password meaning that it’s not possible to distinguish between users.Ī print queue that does not enforce authentication.įor a detailed explanation of print authentication, see Print authentication. However, in some network environments, relying on network level authentication is either not possible, or not reliable.

The print queues also use this authentication and PaperCut NG/MF can trust the supplied identity.

For example, in normal operation, a user logs into a workstation using a domain/network level authentication method such as a username and password. PaperCut NG/MF normally relies on the underlying operating system and the associated print queues to perform authentication.
