I have seen that PaperCut supports internal users. What about internal Groups?
KB Home | I have seen that PaperCut supports internal users. What about internal Groups?
Internal Users are users that are defined in the PaperCut system outside of the network user directory source (e.g. Active Directory, LDAP, etc.) - I.e they are not synchronised into PaperCut, but are manually created - and like Internal Users PaperCut also has the ability to define Internal Groups - again these are groups internal to the PaperCut system, not synchronised from anywhere, but manually created.
Internal Groups are also called “additional groups” as they are usually defined and used ‘in addition’ to the groups already provided by your domain/directory. Additional groups are defined in a text file and may be composed of users who exist either in the domain or are PaperCut Internal Users.
We have created a useful template of this text file, to show you how it works. This template is included within the Program Files of PaperCut on your PaperCut server. See the comments in the text file located here for more information (open in a text editor):
Note: If you are editing the additional-groups.txt.tmpl file to use as your active file for Internal Groups, remember to save it as additional-groups.txt then restart the PaperCut Application Server service. Then you can log into the PaperCut Admin console, go to the Groups tab and click on the “Add/Remove groups” button to find your newly created groups.
In the additional-groups.txt file, you’ll need to have a username associated with the group for it to show under the Groups tab in the PaperCut Admin console. The format of additional-groups.txt is a simple, tab-delimited list of groups and their associated users, with one group and one user, per line, eg:
PaperCut will read this file when it detects a change has been made and then caches the contents in memory.
One of the main use cases of using additional/extra groups in this file is to supplement groups in the user directory. In large education environments, getting new groups defined in a central directory server can be difficult - you need to convince the central administrator that the group is required and needs to be maintained. The manual file method allows groups to be created or controlled by a wider range of people without the need to have admin-level access to the central LDAP/AD server.
Some additional discussion can be found in the manual here.
If you want to bypass the LDAP lookup for adding Groups, and only use the file
Some customers who use LDAP for authentication nonetheless prefer to define their groups solely by using the additional-groups.txt file method instead of relying on LDAP. and we can help you achieve this!
If you prefer to prevent any LDAP searches while executing Add/Remove Groups, you can set the optional advanced configuration key called “user-source.group-list-override-file” to a value of Y.
This config key in found in the Config Editor in - Options > Actions > Config editor (advanced).
This release contains an updated Java version which no longer supports 32-bit workstations. If you have any 32-bit users launching the User Client or Release Station from a network share, see this Knowledge Base article for more information.