Setup Account Based Licensing with username/password

Setup Account Based Licensing with username/password

The second option for account management is to utilize the built-in capabilities of the Zentitle2 platform. This option provides a comprehensive suite of tools for creating and managing user accounts.

The logical flow is to add your "customers," i.e., companies, manually or by import.

Then, within the customer area, add contacts/end users and their associated account authentication details, i.e., "password," in this case vs. Open Id Token when using an iDP.

Then, entitlements can be allocated to these contacts/end users, and they can access the entitlement via their username/password vs. a license code, etc.

The following actions are included in this suite:

• Sending an email with the initial password setup action: Once an account has been created, the platform automatically sends an email to the user. This email contains instructions for setting up their password, providing a secure method for users to establish their account credentials.

• Locking the account after too many invalid login attempts: To protect against unauthorized access, the platform will lock a user's account if there are too many unsuccessful login attempts. This security measure helps to safeguard user accounts from potential threats.

• Resetting the password: The platform provides a reset method if users forget their password or their account is locked out. This can be initiated by the account owner or vendor support, ensuring that users can regain access to their accounts when necessary.

Please follow the subsequent steps for successful account-based licensing integration within Zentitle 2 using the username/password flow.

Configure Password-based ABL

The Account-Based Licensing page is located under the "Administration" > "Configuration" > "Account-Based Licensing" on the top menu.

• In the UI, go to the Account Based Licensing page (inside the Administration section).

• Create a "customer" or select an existing one.

• Navigate to the "ABL" tab under the customer section.

• Click the "add" button on the top right of the page.

• Now, you can either select an existing contact from the dropdown list (one with ABL attached yet) or add a fresh contact by clicking the "add contact" button.

• In this example, we will pick one from the existing contacts list.

• Then select if they are a "user" or an "admin," and the "Authentication type" is set to Password.

• Click save to add this contact to the ABL list.

  • Zentitle2 will immediately send an invitation email to the user at the provided email address, which will also be used as the username for authentication.

---

Attach the contact to an entitlement.

Once the ABL contact (under a customer) is in the system and ready to use, they must be attached to an entitlement in Zentitle if they want to access their software rights.

• Create an entitlement, or use an existing one, and allocate it to the customer to whom the contact belongs. This is a required step.

• You can't allocate an entitlement to an end-user unless the parent company is attached to an entitlement first.

• Once on the entitlement you wish to allocate to a user, navigate to the "ABL" tab at the top of the page.

• Then, select the end user to assign from the dropdown list in the top right of the page.

• Then click the "add" button to the right of the drop-down box to allocate the user to the entitlement.

• The task is complete, and you can see the end-user associated with the entitlement. They can access it via the set username and password they were emailed. On first use, they will authenticate with Zentitle2 and be able to start using their application and associated rights per the entitlement.

---

Password policy

The default password policy for all tenants with

• min length: 8

• require one lowercase character

• require one uppercase character

• require one number

• require one special character

---

Setting up your client application

To enable your app. to authenticate end users via password type ABL, execute an API call in your app. as below:

[POST] {licensing_api_url}/activate with body

{
  "productId": "prod_vs1ueDlrLU61_HIIeDrTjA",
  "activationCredentials": {
    "type": "password",
    "username": "user",
    "password": "pass"
  },
  "seatId": "demoSeatId",
  "seatName": "demoSeatName"
}

The seat name is optional. Seat ID is a fingerprint, so it is not human-readable.

The Seat name could be a computer name or any identifying data you want to add to the record.

The rest of the client application logic related to licensing is the same as using an activation code to enable a user on an entitlement.