Skip to content

Commit 16ea1e6

Browse files
Merge branch 'development' into BLAZ-967323-UGReview
2 parents 51193e8 + b522142 commit 16ea1e6

File tree

2 files changed

+51
-0
lines changed

2 files changed

+51
-0
lines changed

blazor-toc.html

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -105,6 +105,9 @@
105105
<li>
106106
<a href="/blazor/getting-started/license-key/how-to-register-in-a-razor-class-library">Register License Key in a Razor Class Library Application</a>
107107
</li>
108+
<li>
109+
<a href="/blazor/getting-started/license-key/how-to-register-syncfusion-license-securely-in-blazor-wasm-app">How to Register Syncfusion License Key Securely in Blazor WASM App?</a>
110+
</li>
108111
<li>
109112
<a href="/blazor/getting-started/license-key/CI-license-validation">How to Validate Syncfusion License Key In CI Services?</a>
110113
</li>
Lines changed: 48 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,48 @@
1+
---
2+
layout: post
3+
title: How to Register Syncfusion License Key Securely in Blazor WASM App?
4+
description: Learn how to securely register a Syncfusion license key in your Blazor WebAssembly (WASM) application.
5+
platform: Blazor
6+
component: Common
7+
documentation: ug
8+
---
9+
10+
# Secure Registration of Syncfusion License Keys in Blazor WebAssembly Applications
11+
12+
Securely managing license keys in Blazor WebAssembly (WASM) applications is essential to prevent unauthorized access and ensure compliance. Registering a license key in the `Program.cs` file exposes it in the browser through DLLs, creating security risks.
13+
14+
## Recommended Solution: Use Licensed NuGet Packages
15+
16+
Syncfusion recommends using licensed NuGet packages, distributed with the licensed Blazor Product in Volume and Service Pack (SP) releases. These packages eliminate the need to register the license key in the application code.
17+
18+
### Benefits of Using Licensed NuGet Packages
19+
20+
- **Enhanced Security:** Prevents license key exposure in the browser.
21+
- **Simplified Deployment:** Removes the need for manual license key registration.
22+
23+
## Reference: Syncfusion Blazor Web Installer User Guide
24+
25+
Refer to the Syncfusion documentation to download and install the licensed Blazor Product:
26+
27+
- [Download Instructions](https://blazor.syncfusion.com/documentation/installation/web-installer/how-to-download)
28+
- [Installation Guide](https://blazor.syncfusion.com/documentation/installation/web-installer/how-to-install)
29+
30+
These steps ensure secure and compliant Blazor WASM applications, preventing license key exposure.
31+
32+
## Using Licensed NuGet Packages
33+
34+
Build your Blazor WASM application using licensed NuGet packages from these sources:
35+
36+
- **Local Folder:** Store packages locally and configure your project for restoration.
37+
- **Private Repository Manager:** Host and manage packages using a private NuGet repository manager like Nexus.
38+
39+
## Securely manage Syncfusion license keys using Azure Key Vault
40+
41+
You can integrate Azure Key Vault into your application to retrieve the license key at runtime, ensuring it is never exposed in the browser or stored in the client-side code.
42+
43+
For enhanced security, especially in cloud-hosted environments, store and access license keys securely using Azure Key Vault. This method keeps sensitive information out of your source code and configuration files.
44+
45+
Integrate Azure Key Vault to retrieve the license key at runtime, preventing browser exposure or storage in client-side code.
46+
47+
For detailed steps, refer to:
48+
[Securely Store and Use Syncfusion License Keys in Azure Key Vault](https://help.syncfusion.com/common/essential-studio/licensing/licensing-faq/how-to-securely-store-and-use-syncfusion-license-keys-in-azure-key-vault)

0 commit comments

Comments
 (0)