# Mapping Usernames to a Group

# Introduction

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

# Configuring license-user-mapping

  1. 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.

  2. 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 Optimize 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.

  3. Save the changes.

  1. 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.

  2. 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 Optimize 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.

  3. Save the changes.

# Next Steps?

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

   Data Generation  

We value your feedback!

Please take a few minutes to complete our survey and share your thoughts on your recent experience with our documentation.

Take survey

Close