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

MSL items may be automatically authorized to be on any asset that is found in a given status.  This capability is over-ridden by Configuration Item-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).

If one or more asset types have been selected in the MSL setting for contstraining status-based authorization, then only those asset types will participate in status-based authorization.

If the MSL setting for constraining status-based authorization has been left blank (nothing selected), and the global setting SLMSWBearingAssetTypes is not blank, then only the asset types in the global setting will participate in status-based authorization.  If that setting is blank, then all asset types found in the matching status will participate.

To set up status-based authorization, you must edit the MSL item(s) that you want to be automatically authorized when an asset is found to be in a given status.  If you have appropriate access, select Managed Software from the left menu, find the MSL item you wish to configure for status-based authorization, edit the record, and then set the "Automatically authorize for assets in this status" setting to the proper status value.  Save your changes.

Status-based authorization is performed by Consolidate.  The next time Consolidate runs, and each subsequent time, any assets found to be in the status you set will have the MSL item automatically authorized.

Notes:

1.Status-based authorization only applies to MSL titles that have been set to assign authorizations to the device.

2.Any form of authorization will stage a charge, based on the current settings.  Status-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.Status-based authorization will only authorize a single instance (instance #0).