Licensing For SCIM Enabled Users

QMetry allows the admin to choose how to manage user license types, either automatically or manually. The admin can select from the following options:

  • Automatic Management: QMetry automatically assigns and manages user license types based on the user's assigned projects, roles, and available licenses.

    • If a user is assigned only read-only roles for all projects, QMetry automatically assign a "Read-Only" license, provided there are available Read-Only licenses.

    • If a user has at least one project with a non-read-only role, QMetry automatically assigns a "Regular" license, as long as Regular licenses are available.

  • Manual Management: The SCIM administrator can manually assign and manage user license types using the custom attribute QMetry_User_LicenseType.

Allotting and Managing User License Types (Regular or Read-Only)

To allot and manage license types for SCIM enabled users, perform the following steps:

QPro_SCIM_Licensing.png
  1. Go to System Settings.

  2. Select SCIM.

  3. Enable SCIM Provisioning.

  4. Under Allot and Manage License Type (Regular or Read-Only) to Users, select one of the following options:

    • Manual management by the SCIM administrator

    • Auto-allotment and manage License Type

Understanding Scenarios for Automatic User License Management in QMetry

QMetry intelligently assigns and manages user licenses based on the user's assigned projects, roles, and available licenses. Below are different scenarios outlining how licenses are allotted:

Table 2. Scenario A - Has Sufficient Regular Licenses and Read Only License Remaining.

Scenario

User License Action

Activation Status

A New User is created with Read Only role assigned to all projects

Read Only

User Active.

A New User is created with all Non-Read Only roles (Admin, Tester, QA Manager, etc.) assigned to projects.

Regular

User Active.

User Update (Current License: Read Only)

User has All Project Access as Read Only and a new Project with Read Only is assigned

Read Only

Older projects remain as assigned.

New project/role are assigned as Read Only.

User has All Project Access as Read Only Role and a new/existing Project with Non Read Only Role is assigned

License Type Changed to Regular

Older projects remain as assigned.

New/updated project/role are assigned.

User Update (Current License: Regular)

User has All Project Access as Non-Read Only Role and a new Project with Non-Read Only Role is assigned

Regular

Older projects remain as assigned.

New/updated project/role are assigned.

User has All Project Access as Non-Read Only Role and a new Project with Read Only Role is assigned

Regular

Older projects remain as assigned.

New project/role are assigned.

The user has all projects assigned/updated as Read Only Role

License Type Changed to Read Only

Older projects remain as assigned, after the project with non-read-only role is removed.

Assign updated new project/role.



Table 3. Scenario B - Has Sufficient Regular Licenses and No Read Only License Remaining/Not Purchased.

Scenario

User License Action

Activation Status

New User is created with Read Only role assigned to all projects

Regular License

User Active.

New User is created with any 1 Non Read Only role (Admin, Tester, QA Manager, etc.) assigned to any projects

Regular License

User Active.

User Update (Current License: Read Only)

User has All Project Access as Read Only Role and a new Project with Read Only Role is assigned

Read Only

Older projects remain as assigned. Assign the new project/role.

User has All Project Access as Read Only Role and a new/existing Project with Non Read Only Role is assigned

License Type Changed to Regular

Older projects remain as assigned. Assign the new/updated project/role. For auto-conversion audit log should be recorded.

User Update (Current License: Regular)

User has All Project Access as Non Read Only and a new Project with Non Read Only Role is assigned

Regular

Older projects remain as assigned.

Assign the new project/role.

User has All Project Access as Non Read Only Role and a new Project with Read Only Role is assigned

Regular

Older projects remain as assigned.

Assign the new project/role

User has all projects assigned/updated as Read Only Role

Keep License Type as Regular

Older projects remain as assigned, after the project with non-read only role is removed.

Important - SCIM Admin need to Push the Group under Push Groups tab or have to assign/unassign the project to same user.



Table 4. Scenario C - Regular Licenses Exhausted and Read Only License are available.

Scenario

User License Action

Activation Status

New User is created with Read Only role assigned to all projects

Read Only

User Active.

New User is created with any 1 Non Read Only role (Admin, Tester, QA Manager, etc.) assigned to any projects

Error - Active regular user limit exceeded. Please contact your QMetry admin to increase license limit or deactivate other users.

-

User Update (Current License: Read Only)

User has All Project Access as Read Only Role and a new Project with Read Only Role is assigned

Read Only

Older projects remain as assigned. Assign the new project/role.

User has All Project Access as Read Only Role and a new/existing Project with Non Read Only Role is assigned

Read Only.

Error - QMetry could not automatically update the user license type to ‘Regular’ because the current limit for Regular license has been exhausted. To resolve this issue, please either deactivate existing Regular license users or purchase additional licenses.

Older projects remain as assigned. Assign the new/updated project/role. For auto-conversion audit log should be recorded.

User Update (Current License: Regular)

User has All Project Access as Non Read Only Role and a new Project with Non Read Only Role is assigned

Regular

Older projects remain as assigned. New project/role are assigned.

User has All Project Access as Non Read Only Role and a new Project with Read Only Role is assigned

Regular

Older projects remain as assigned.

Assign the new project/role

User has all projects assigned/updated as Read Only Role

License Type Changed to Read Only

Older projects remain as assigned, after the project with non-read-only role is removed. Assign updated the new project/role.



Publication date: