Set the method that Print Deploy uses to determine the user’s identity
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.
The method used to determine the user identity is set in the UserIdentityMethod config key.
You can update the UserIdentityMethod config key in two ways:
-
Via the Settings tab in the Print Deploy admin interface. This method does not require a restart.
-
Via the client.conf.toml file located in:
<application-server-path>\providers\print-deploy\win\data\config.Any change to the client.conf.toml file require a PaperCutPrint Deploy Server service restart.
Config key values | |
---|---|
PROMPT |
When the Print Deploy client is first installed, a once-off login popup is displayed. The user has to enter their PaperCut credentials before the print queues are installed. By default, the user is given the option to use their PaperCut username and password. To support other forms of credentials, for example Google identity, see Configuring login options |
TRUST |
Print Deploy uses the logged-in user’s identity for authentication purposes. |
AUTO |
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.
Configuring login options
By default the user can use their PaperCut username and password to log in. To support other forms of login credentials, you can modify the config key AuthMethods, available since v1.5 (October 2020).
You can update the AuthMethods config key in two ways:
-
Via the Settings tab in the Print Deploy admin interface. This method does not require a restart.
-
Via the client.conf.toml file, located in:
<application-server-path>\providers\print-deploy\win\data\configAdd or update this line accordingly:
AuthMethods = ["google", "username"]
Any change to the client.conf.toml file requires a PaperCutPrint Deploy Server service restart.
You need to enable at least one option:
Options for AuthMethods | |
---|---|
username |
Provides the user with the option to log in using their PaperCut username and password. |
|
Provides the user the option to log in using their Google credentials. It adds a Continue with Google button in the PaperCut Print Deploy client's login screen. If there's no user in PaperCut NG/MF associated with the email address used for logging in, the authentication will fail. For Google authentication, the User Identity method must be set to PROMPT. For more information, take a look at Synchronize user and group details with Google Cloud Directory. |