You can choose whether users will receive a once-off authentication popup when the Print Deploy client starts up for the first time. This once-off authentication is useful in environments where users’ computers are not joined to a local domain, for example, G Suite or Azure AD environments.
Print Deploy automatically detects whether a computer is joined to a domain, and if it is, it will not authenticate the user and instead use the identity of the logged-in user.
If this is not the behavior you want, you can configure Print Deploy to either always trust the identity of the logged-in user, or always prompt for an authentication. The latter is especially useful in environments like shared office spaces where a computer might be joined to a domain, but it is a different company’s domain and you do not want to trust that identity.
Use the config key UserIdentityMethod.
Update the UserIdentityMethod config in the client.conf.toml file, located in: <application-server-path>\providers\print-deploy\win\data\config.
Any changes to this config requires a PaperCutPrint Deploy Server service restart.
When the Print Deploy client is first installed, a once-off login popup is displayed. The user has to enter their PaperCut username and password before the print queues are installed.
Print Deploy uses the logged-in user’s identity for authentication purposes.
If the computer has domain membership, Print Deploy attempts to determine if it can trust the logged-in user. Else, the login popup is displayed.
Default value: Auto.
In a non-local AD environment, when deploying and installing Mobility Print queues, user authentication is required. The user will be presented with a once-off authentication popup.