Identify Job Authentication Method

Each user in your organization needs to have a unique identifier that is attached to each print job they send, allowing MyQ to recognize them as the sender.

In MyQ, usernames or aliases are used for these purposes. To select the right method for authenticating an incoming print job (and detecting the sending user), first, you should recognize how your users are identified and learn about the available detection methods.

User Detection Options

There are several ways users can be detected from incoming print jobs. The method ideal for your environment will depend on your specific needs, print drivers used in your organization, or even the specific applications users print from.

User Detection Methods

In standard environments, these are the most common job sender detection options used:

• The user detection method “Job sender” will identify the user from the data in the LPR/IPP(S) etc. connection during the reception of the job. This is usually the login name of the user on their computer and usually corresponds to the sAMAccountName attribute in Active Directory. Still, it can also be the userPrincipalName in some scenarios. Select this method when users print through MyQ Desktop Client 10.2 and higher and assign the job to the user signed in the client.

• The user detection method “From PJL” will identify the user from the command you define in the PJL Detection settings of the relevant queue. This helps you to utilize information embedded in the job by the print driver.

• The user detection method “Job name” will identify the user from the filename that is being sent to MyQ. This can be useful, for example, when printing from specific applications.

The other detection options available are tailored to specific use cases.

Determine How to Identify Users from Print Jobs

The easiest way to check if your detection method is working as expected is to test it yourself. This can be simplest when the user you are testing with does not yet exist in MyQ, it will be easier to find in the MyQ log for the user detected from the incoming print job.

1. Create a queue in MyQ with your preferred User detection method.

2. Configure at least one workstation, sign in as an existing user in your user directory, and try to send a job to MyQ.

3. In the Log, you will find the details of the job reception, including the step where MyQ tries to match the job to a MyQ user. Because the user did not exist, the job was not authenticated, and you will see a message: Job discarded. User “john.doe” not found. This is your detected user.

Now, you also can alter the queue’s User detection method and try again.

In mixed-fleet environments where different print drivers are used, you might want to test printing from all these drivers with the PJL detection settings on the queue and adjust it to include all PJL commands that might appear in incoming print jobs.

Decide on the Detection Method

Once you've chosen the appropriate detection method, you can apply this knowledge when setting up the synchronization source. It's essential to ensure that each user in your organization has been allocated a username or aliases that match how their print jobs will be identified by MyQ.