Overview
A named user license (also known as identity-based licensing or user-locked license) ties a license to a specific user, identified by their email address. The user activates the license by logging in with their credentials, so they never enter a license key.
Named user licenses can be either node-locked or hosted floating. Regardless of the type, users must authenticate to access the licenses associated with their account.
Named user licensing is most useful for organizations, where each seat is tied to a specific member who logs in with their own credentials. It also works for standalone users.
Activating a named user license
The user must authenticate before their licenses can be activated. The flow has three steps:
-
Authenticating the user: authenticate the user by calling the
AuthenticateUser(string email, string password)LexActivator API function.If your users log in through an identity provider instead of Cryptlex credentials, authenticate them with the
AuthenticateUserWithIdToken()function using OIDC SSO.If the user has enabled two-factor authentication (2FA), the function fails with the
LA_E_TWO_FACTOR_AUTHENTICATION_CODE_MISSINGerror. Provide the 2FA code withSetTwoFactorAuthenticationCode(), then callAuthenticateUser()again. -
Retrieving the user license: after successful authentication, call
GetUserLicenses()to retrieve the licenses linked to the user, and pass the chosen license key toSetLicenseKey(). If multiple licenses are linked, prompt the user to select one. -
Activating the license: once the license key is set, call
ActivateLicense(). Activation is the same as for regular licenses; refer to the guide for your programming language.