#
Mapping Usernames to a Group
#
Introduction
Configure license-user-mapping
to map user to a group.
Apply the configurations shown in the Open iT server.
#
Configuring license-user-mapping
Open
license-user-mapping
file in the Configuration directory, which is by default inC:\Program Files\OpeniT\Core\Configuration
.Notice that it contains instructions on how to edit the file.
Specify usernames with the following syntax:
MAP: UserGroupName Username1 Username2
Empty lines are allowed — any line beginning with # as the first non-white character is considered a comment. Globbing is also supported. You can use several globbing patterns, but keep in mind that they are slower than exact matches.
In the mapping file, entries are case-insensitive. This means that variations in capitalization, such as 'User' and 'user', will be recognized as identical. Also, both 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.
ExampleMAP: UserGroup1 User07 User29
This example maps User07 and User29 to UserGroup1.
Save the changes.
The mapping file will only affect the data collected after configuring. To apply the mapping for historical data, you need to regenerate that data. This process will help ensure that all your information is aligned and accurate.
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:
MAP: UserGroupName Username1 Username2
Empty lines are allowed — any line beginning with # as the first non-white character is considered a comment. Globbing is also supported. You can use several globbing patterns, but keep in mind that they are slower than exact matches.
In the mapping file, entries are case-insensitive. This means that variations in capitalization, such as 'User' and 'user', will be recognized as identical. Also, both 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.
ExampleMAP: UserGroup1 User07 User29
This example maps User07 and User29 to UserGroup1.
Save the changes.
The mapping file will only affect the data collected after configuring. To apply the mapping for historical data, you need to regenerate that data. This process will help ensure that all your information is aligned and accurate.
- (46) Individual License Use v2.0
- (47) Host License Use v2.0
- (49) Host User License Use
- (50) Host User License Use Logfile
- (61) Individual License Queued
- (62) Host User License Use Logfile
- (72) Hostgroup License Use v2.0
- (75) License Logfile Events
- (77) Individual Queued Logfile
- (83) Host License Use Logfile
- (84) Individual License Use Logfile
- (104) License Logfile Events v2.0
- (127) License Host User Usage Distinct Host
- (129) FlexNet Log Events
#
Next Steps?
Proceed with data regeneration after configuring all the necessary mapping files to apply the changes in the historical reports: