<< Click to Display Table of Contents >> Navigation:  Modules > Asset Management > Software License Management > Authorizing Software > Configuration Item-based Authorization

MSL items may be automatically authorized to be on any asset that carries a Configuration Item (CI) Number that matches a currently defined Configuration Item (CI).  The matched CI must also have one or more MSL applications defined as part of its definition.  This capability is overrides Status-based authorization, and is generally used to automatically authorize core MSL applications to be on newly received assets (assets that have been received but have not yet been discovered by autodiscovery).

To set up Configuration Item-based authorization, you must enter one or more CI definitions.  Assuming you have proper access, choose the Configuration Items child menu option from the Assets left menu.  Assign a CI number along with the appropriate MSL applications and save your changes.  Make sure the CI number you defined matches the CI number being carried in the target asset record(s).  You may either directly edit each asset record via the User Interface, or you may use the ASN processor to forward CI numbers fed by vendors from the ASN through to the MIE's asset table.

Configuration Item-based authorization is performed by Consolidate.  The next time Consolidate runs, and each subsequent time, any assets matching defined CIs that also have defined MSL item(s) will have the MSL item(s) automatically authorized.  Once an asset is CI-authorized, it will not be processed for CI authorization again (CI authorization happens only once in the life cycle of the asset).

Notes:

1.Configuration item authorization applies only to MSL titles that have been set to assign authorization to the device.

2.Any form of authorization will stage a charge, based on the current settings. Configuration Item-based authorization does stage a charge for the MSL item.

3.Authorization will only occur if the MSL item isn't already authorized to be on the asset (and hence only one charge will be staged).

4.If Status-based authorization and Configuration Item-based authorization both apply for the same asset (asset record carries a CI number matching an active definition with MSL items defined AND the asset is currently in a status defined by one or more MSL items for auto-authorization), only Configuration Item-based authorization will be honored.  The asset will NOT be authorized for MSL items via both Status-based and Configuration Item-based authorization.

5.CI-based authorization will only authorize a single instance (instance #0).

6.CI-based authorization is performed only once in the lifetime of the asset.

7.CI-based authorization will not be performed if the asset is currently in a status that matches one of the defined status-harvest settings.  (Otherwise, the authorization would be immediately harvested).