Vaadin licensing FAQ and troubleshooting
Second, double check you are using the subscription key that matches your subscription. You can find your subscription key in the license management.
Third, make sure that the correct application is deployed.
I am getting “The provided license key does not allow usage of [...]” error message. What should I do?
This means that you either
- did not provide a valid license key during build time,
- the product is not part of your subscription or
- the license checker could not verify your license for other reasons
First, check if the commercial product is actually part of your subscription.
Second, verify if your API key (proKey) exists or offline key is up to date. In case of CI/CD build verify the server license key is valid.
Sometimes company firewalls block requests to tools.vaadin.com or maven.vaadin.com. Either ask your administrator to open the firewall or set up a local Maven repository and use offline keys.
In the second case we recommend contacting your sales contact or customer support at Vaadin to discuss the situation.
Yes but not immediately! This only happens if either we cannot get in contact with you so that we cannot negotiate new limits or if the negotiations failed. In both cases the DAU limit will be enforced after the grace period ends. Your application will still be usable but will block users when the limit is hit.
Daily Active User represents a human end-user for one application that you built with Vaadin and run in production mode, during a 24-hour period.
This includes anonymous users or authenticated users but also test users for integration testing if they interact with the application for at least a minute. Just visiting a view and closing the browser will not be counted as DAU.
Check our documentation for instructions on how to optimize your DAU counting.
First, check your subscription state and if the license validation works. If not, either your company's license administrator has not yet assigned a seat for you, or the license is no longer valid.
The licenses for commercial components are checked through your vaadin.com login. The first time you are using a commercial product, it will ask you to log in to vaadin.com to validate your license. You only need to manually install the license key when running on a CI/build server or when you want to work offline.
Extended Maintenance
When using the latest Extended Maintenance releases the new license checker version is used for the framework product itself. This applies to versions Vaadin 7.7.17 and newer, Vaadin 8.14.3 and newer respectively. Follow the same guidance as described in https://vaadin.com/myaccount/licenses#latest
Furthermore from version 7.7.37 and respectively 8.20.2 the widgetset compilation phase has been updated to use the new license checker as well. Hence Charts, Spreadsheet, Touchkit or Board will no longer require specific license key. The server / offline key is used instead.
Additionally TestBench version 5.3.0 and newer uses the new license checker.
When using Designer with Vaadin 7 or 8, or TestBench 4 with Vaadin 7 the old product specific keys are used, see the next chapter.
Older versions
Vaadin 6/7/8 license check is done through license keys. Please find your license keys from https://vaadin.com/pro/licenses. Click on a license key to obtain the purchased key. Note: a new set of keys will be generated with every subscription renewal.
To install the license key in a development workstation, you can copy and paste it verbatim to a file in your home directory
License for each product has a separate license file as follows:
Vaadin Charts
.vaadin.charts.developer.license
Vaadin Spreadsheet
.vaadin.spreadsheet.developer.license
Vaadin TestBench
.vaadin.testbench.developer.license
You can also pass the key as a system property to the widget set compiler, usually with a -D option. For example, on the command-line:
java -Dvaadin.<product>.developer.license=L1cen5e-c0de …
I am getting “This application is using components which are a part of a Vaadin subscription” error message. What should I do?
Clear Vaadin cookies and try again.
Please make sure that you use the same window.
Adblocker or 3rd party cookie denial could be blocking the license check. However, the error message only appears in development mode when in localhost. When the application is deployed into production and accessed from outside it will not show, thus the message will not visible to the end users of the application.
If you want to be certain you're not using anything commercial, then you can change the main dependency to vaadin-core
instead of vaadin
in your pom.xml
or build.gradle
file.
I have a perpetual license for Designer 2, but after updating Designer I’m asked for a Pro subscription?
A known error in SSLHandshakeException (Reported by users of WebSphere Liberty and WildFly in Docker) : https://vaadin.com/forum/thread/18444677/running-mpr-project-on-websphere-liberty-fails-with-suncertpathbuilderexcep
Please also check other known limitations for Multiplatform runtime usage here https://vaadin.com/docs/latest/tools/mpr/configuration/limitations
In case you are a license owner or administrator you can assign licenses to developers in the team management view.
Depending on your build tool you either have a
a) pom.xml
file (Maven)
Look for a vaadin.version
property there. If you can’t find the property, check if there is
- a
vaadin-bom
dependency. Its version is the Vaadin version. - a
vaadin-server
dependency. Its version is the Vaadin version.
b) build.gradle
file (Gradle)
There is a vaadin {
block that has the version number.
c) ivy.xml
file (Ivy)
There is something like <!ENTITY vaadin.version "7.6.5">
which shows the version.