User authentication
Covers different ways that you can authenticate customers using user credentials instead of license keys.
Introduction
The easiest way to authenticate end users is by using a 20 character long license key. This allows you to restrict which features your clients have access to, the expiry date, and more.
If you anticipate that your clients will have many licenses, or if you prefer to authenticate them using username and password, Cryptolens supports several ways to accomplish this.
Approaches
Method 1: If you are using the Customer portal and your customers have an account with us, you can use this approach. A new browser window will open where the customer can authenticate, allowing you to retreive all their licenses inside your application once authentication succeeds. Currently supported out of the box in .NET.
Method 2: If you have assigned licenses to a Customer object in the portal, you can also authenticate them inside your application. This is covered in this article. This approach allows you to contol the user experience and customers do not need to have access to the customer portal. Currently supported out of the box in .NET and Python, and support for more languages is coming soon.
Method 3: If your customer has many licenses and you want to issue them one main license, you can use this approach. This is similar to Method 2, except that users authenticate using a long string value instead of user name and password.
Method 4: If you would like to limit the number of users that many use a certain license, you can use this approach. This is different from Method 1-3, where the goal was to make it easier for users to have many licenses and not have to keep track of them. In Method 4, the idea is to limit concurrent use based on users and not machine code.
User authentication
Covers different ways that you can authenticate customers using user credentials instead of license keys.
Introduction
The easiest way to authenticate end users is by using a 20 character long license key. This allows you to restrict which features your clients have access to, the expiry date, and more.
If you anticipate that your clients will have many licenses, or if you prefer to authenticate them using username and password, Cryptolens supports several ways to accomplish this.
Approaches
Method 1: If you are using the Customer portal and your customers have an account with us, you can use this approach. A new browser window will open where the customer can authenticate, allowing you to retreive all their licenses inside your application once authentication succeeds. Currently supported out of the box in .NET.
Method 2: If you have assigned licenses to a Customer object in the portal, you can also authenticate them inside your application. This is covered in this article. This approach allows you to contol the user experience and customers do not need to have access to the customer portal. Currently supported out of the box in .NET and Python, and support for more languages is coming soon.
Method 3: If your customer has many licenses and you want to issue them one main license, you can use this approach. This is similar to Method 2, except that users authenticate using a long string value instead of user name and password.
Method 4: If you would like to limit the number of users that many use a certain license, you can use this approach. This is different from Method 1-3, where the goal was to make it easier for users to have many licenses and not have to keep track of them. In Method 4, the idea is to limit concurrent use based on users and not machine code.