Cryptlex Documentation
  • Welcome to Cryptlex!
  • Getting Started
    • Overview
    • Licensing Models
  • License Management
    • License Templates
    • Implementing License Models
    • Creating Licenses
    • License Subscriptions
    • Custom License Fields
    • Meter Attributes
    • Suspending Licenses
    • Revoking Licenses
    • Maintenance Policies
  • Feature Management
    • Overview
    • Features and Entitlement Sets
    • License Feature Entitlements
    • Accessing Feature Entitlements
    • Use Cases
  • User Management
    • Roles
    • Creating Users
    • Authenticating Users
    • Organizations
    • Resellers
    • Customer Portal
    • Reseller Portal
    • Google SSO
    • SAML SSO
  • Release Management
    • Overview
    • Creating Releases
    • Distributing Releases
  • Node Locked Licenses
    • Overview
    • Using LexActivator
      • Using LexActivator with C, C++ and Objective C
      • Using LexActivator with C#
      • Using LexActivator with VB.NET
      • Using LexActivator with Java
      • Using LexActivator with Delphi
      • Using LexActivator with Python
      • Using LexActivator with Go
      • Using LexActivator with Node.js
      • Using LexActivator with Ruby
      • Using LexActivator with Android
      • Using LexActivator with iOS
      • Using LexActivator with Flutter
    • Using Web API
    • Offline Activations
    • Proxies and Firewall
  • Floating Licenses
    • Overview
    • Hosted Floating License Server
    • On-Premise Floating Licenses
      • LexFloatServer
      • Using LexFloatClient
        • Using LexFloatClient with C, C++ & Objective C
        • Using LexFloatClient with C#
        • Using LexFloatClient with VB.NET
        • Using LexFloatClient with Java
        • Using LexFloatClient with Delphi
        • Using LexFloatClient with Python
        • Using LexFloatClient with Node.js
        • Using LexFloatClient with Go
        • Using LexFloatClient with Android
        • Using LexFloatClient with iOS
      • Offline Floating License
  • Named User Licenses
  • Timed Trials
    • Verified Trials
    • Unverified Trials
  • Licensing Docker Apps
  • Webhooks
  • Automated Emails
  • Web Integration
    • Personal Access Tokens
    • Using Web API
    • Using Zapier
    • Using FastSpring
    • Custom Development
  • Changelog
    • Web API
    • LexActivator
    • LexFloatClient
    • LexFloatServer
  • Legal
    • Terms of Service
    • Privacy Policy
    • Subprocessors
    • Data Processing Addendum
    • Service Level Agreement
    • Security, Privacy, and Compliance
    • Open Source Licenses
  • Cryptlex On-Premise
    • Overview
    • System Requirements
    • Server Layout
    • Installation Guide
      • Docker Compose
      • Kubernetes
    • Configuring Client Libraries
    • Monitoring and Error Reporting
Powered by GitBook
On this page
  • 1- Authenticating the user
  • 2- Retrieving the user license
  • 3- Activating the license

Named User Licenses

PreviousOffline Floating LicenseNextTimed Trials

Last updated 10 months ago

A named user license is a licensing model in which the software or service is allocated to a specific individual, typically identified by a unique email address.

This model necessitates license activation using the designated user's credentials, moving away from the traditional use of license keys.

Named user licenses can be either node-locked or floating. Regardless of the type, users must authenticate to access the licenses associated with their account. The typical process involves the following three steps:

1- Authenticating the user

User authentication is achieved by calling the AuthenticateUser(string email, string password) LexActivator API function.

In scenarios where users have enabled two-factor authentication (2FA), executing the function results in a LA_E_TWO_FACTOR_AUTHENTICATION_CODE_MISSING exception. In such instances, it becomes necessary to provide the 2FA code using the SetTwoFactorAuthenticationCode() LexActivator API function.

Once the 2FA code has been set, you need to call the AuthenticateUser() LexActivator API function again.

2- Retrieving the user license

Upon successful user authentication, GetUserLicenses() LexActivator API function can be used to retrieve licenses associated with the user. The acquired license key can then be passed to the SetLicenseKey() LexActivator API function for further processing. In scenarios where multiple licenses are linked to a particular user, it is possible to prompt the user's selection of any license for activation purposes.

3- Activating the license

Once the license key is obtained, the subsequent activation procedure aligns closely with the guidelines provided in the documentation for each respective . To activate the license within your application, simply call the ActivateLicense() function from the LexActivator API.

programming language