Adding aliases for usernames
Last modified on 11 August 2020 05:25 PM
In some scenarios, a particular user wants to print a job but his/her username has been changed for various reasons and it is reflected in PaperCut now as a different username. Examples of why the username may have changed:
What can one do?
To workaround this problem PaperCut allows users to have a list of aliases for their username. There are three options available:
Sync aliases using AD/LDAP
To set up the automatic sync of aliases using AD/LDAP, you will need to enable
Once Username Aliasing has been enabled, you will see a new text field on the User Details page.
This information can be automatically imported from Active Directory or LDAP during an overnight sync. Once Username Aliasing is enabled, an option to enter an AD/LDAP field name appears under Options → User/Group sync. Any valid Active Directory or LDAP user field can be chosen to import this information e.g. employeeNumber, employeeID, otherLoginWorkstations.
Once this has been set, information from the Active Directory or LDAP field will be imported every night as username aliases. For more information on user group synchronization see the section called “User and Group Synchronization”.
Text file option
So John O’Hare (username “john_o_hare”) can have username aliases of “johnohare”, and “johare”. The aliases information is kept in a file,
and can be created based on the provided template file,
For example on Windows:
johno'hare: john_o_hare johare: john_o_hare
The format of the alias file is:
aliasname1: username1 aliasnameA: username2 aliasnameB: username2
where aliasname is mapped to username in the system database. A user may have multiple aliases. In this example, username2 is known both as aliasenameA and aliasnameB. The separator between aliasname and username can be “:”, “=“ or tab.
Update aliases using web services API or the server-command utility
You can also obtain the value of the user alias using the corresponding
At what level is the alias applied?
The username aliases are applied at the following levels:
Note: If you add “admin” as an aliased user, you may not be able to access the PaperCut Administration Console.
What happens if the username does not exist in the alias file?
If a username does not match in the alias file it’s assumed the user is a standard username. If the user is new to the entire system it will be managed as a new user account and automatically created in PaperCut as per your new user rules defined under the groups section (group level initial user creation rules). For this reason you should take care to ensure your alias list is current and up-to-date.