Version: 10.2

Usernames to Group Mapping

Introduction

Configure license-user-mapping to map users to a group.

warning

Apply the configurations shown in the Open iT Core Server.

Open license-user-mapping file in the Configuration directory, which is by default in C:\Program Files\OpeniT\Core\Configuration.

Notice that it contains instructions on how to edit the file.
Specify usernames to group with the following syntax:
Mapping Syntax
```
MAP: <UserGroupName>
<Username1>
<Username2>
```
Empty lines are allowed — any line beginning with # as the first non-whitespace character is considered a comment. Globbing is also supported, allowing you to use several globbing patterns; however, remember that they are slower than exact matches. To make your mapping files more effective and efficient, refer to the Optimizing Rules to Speed Up Rename or Mapping page.

In the mapping file, entries are case-insensitive, meaning that capitalization variations, such as 'User' and 'user', will be recognized as identical. Also, note that leading and trailing spaces are removed from entries.

Each user can be a member of only one group. A user that appears in multiple mappings will always be mapped to its first occurrence in the file.
Example
```
MAP: UserGroup1    
User07
User29
```
This example maps User07 and User29 to UserGroup1.

You can also include custom configurations in this mapping file, such as default mapping, setting date limits on specific mapping entries, or creating nested maps.
Save the changes.

Open license-user-mapping file in the etc directory, which is by default in /var/opt/openit/etc.

Notice that it contains instructions on how to edit the file.
Specify usernames with the following syntax:
Mapping Syntax
```
MAP: <UserGroupName>
<Username1>
<Username2>
```
Empty lines are allowed — any line beginning with # as the first non-whitespace character is considered a comment. Globbing is also supported, allowing you to use several globbing patterns; however, remember that they are slower than exact matches. To make your mapping files more effective and efficient, refer to the Optimizing Rules to Speed Up Rename or Mapping page.

In the mapping file, entries are case-insensitive, meaning that capitalization variations, such as 'User' and 'user', will be recognized as identical. Also, note that leading and trailing spaces are removed from entries.

Each user can be a member of only one group. A user that appears in multiple mappings will always be mapped to its first occurrence in the file.
Example
```
MAP: UserGroup1    
User07
User29
```
This example maps User07 and User29 to UserGroup1.

You can also include custom configurations in this mapping file, such as default mapping, setting date limits on specific mapping entries, or creating nested maps.
Save the changes.

This mapping may affect the following data types:

Proceed with data regeneration after configuring all the necessary mapping files to apply the changes in the historical reports: