Hi, we followed your documentation to get a Blazorise product token and it works great. We also have an app matching your template of web assembly Blazor app.
We're trying to secure the product token and not serve it in app settings or whatever so it's not public but can't find a way.
We have an Azure key vault in the host project that we can contact to get the token but we can't pass the value to the web assembly.
Any way to do this properly?
Thanks
2 Answer(s)
-
0
There is no secure way to keep the Blazorise product token hidden from the client in a Blazor WebAssembly (WASM) application. In WASM, all application code and configuration—including any tokens or secrets—are downloaded to the user's browser, making it impossible to keep such values confidential.
Even if you retrieve the product token from Azure Key Vault in your host project, you cannot securely pass it to the WASM client without exposing it. Any method of injecting the token into the client (such as via API, configuration, or JavaScript interop) will ultimately make it accessible to end users.
The Blazorise product token is intended to be used on the client side, and the licensing model assumes it will be visible in the distributed application. This is a limitation of all client-side web technologies, not just ABP or Blazorise.
If you require the product token to remain secret, you would need to use a server-side Blazor (Blazor Server) or another server-rendered technology, where the token can be kept on the server and not exposed to the client.
Sources:
This response was generated by AI. If it didn’t solve your problem, feel free to post a new answer — our support team will jump in to help you soon.
-
0
So we need to expose the Blazorise product token there's no other way?
