Application Sign-in to Vendor License Mapping

Introduction

The application sign-in to vendor license mapping file is used to correlate application sign-in events collected from identity providers (IdPs) with vendor license usage data.

This mapping allows the system to unify authentication data and usage data, enabling more accurate reporting, analysis, and attribution of vendor license usage.

note

This mapping file is crucial for generating complete details in the Entitled User Sign-In Signals portlet.

warning

Apply the configurations shown in the Open iT Core Server.

Configuring `idp-app-to-product.map`

Windows
Unix

Open idp-app-to-product.map 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 the vendor license name and application names using the following syntax:
Mapping Syntax
```
MAP: <VendorLicense_Name>   
<App_Registration_Name>
```
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 Optimizing Rules to Speed Up Rename or Mapping.

In the mapping file, entries are case-insensitive, meaning that capitalization variations, such as '3dExperience' and '3DExperience', will be recognized as identical. Also, note that leading and trailing spaces are removed from entries.
Example
```
MAP: WIN-HOST01;solidoworks
3DEXPERIENCE WORKS Learner
3DSwymer
Collaborative Industry Innovator
```
This example sets WIN-HOST01;solidoworks as the vendor license name for 3DEXPERIENCE WORKS Learner, 3DSwymer and Collaborative Industry Innovator.

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 idp-app-to-product.map 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 the vendor license name and application names using the following syntax:
Mapping Syntax
```
MAP: <VendorLicense_Name>   
<App_Registration_Name>
```
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 Optimizing Rules to Speed Up Rename or Mapping.

In the mapping file, entries are case-insensitive, meaning that capitalization variations, such as '3dExperience' and '3DExperience', will be recognized as identical. Also, note that leading and trailing spaces are removed from entries.
Example
```
MAP: WIN-HOST01;solidoworks
3DEXPERIENCE WORKS Learner
3DSwymer
Collaborative Industry Innovator
```
This example sets WIN-HOST01;solidoworks as the vendor license name for 3DEXPERIENCE WORKS Learner, 3DSwymer and Collaborative Industry Innovator.

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:

Next Steps?

Proceed with data regeneration after configuring all the necessary mapping files to apply the changes in the real-time and historical reports.

For historical reports:

Data Generation

Introduction​

Configuring idp-app-to-product.map​

Next Steps?​

Introduction

Configuring `idp-app-to-product.map`

Next Steps?