Skip to content

Commit 7fcec45

Browse files
authored
Updates
1 parent b42af11 commit 7fcec45

File tree

1 file changed

+8
-8
lines changed

1 file changed

+8
-8
lines changed

aspnetcore/blazor/progressive-web-app/push-notifications.md

Lines changed: 8 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,6 @@
11
---
22
title: Push notifications for ASP.NET Core Blazor Progressive Web Applications (PWAs)
3+
ai-usage: ai-assisted
34
author: guardrex
45
description: Learn how to issue push notifications in Blazor Progressive Web Applications (PWAs).
56
monikerRange: '>= aspnetcore-3.1'
@@ -37,14 +38,13 @@ Placeholders used in this article's example code:
3738

3839
For this article's C# examples, update the `[email protected]` email address to match the address used when creating the custom key pair.
3940

40-
> [!IMPORTANT]
41-
> When implementing push notifications, ensure that cryptographic keys are managed securely:
42-
>
43-
> * **Key generation**: Use a trusted library or tool to generate the public and private keys. Avoid using weak or outdated algorithms.
44-
> * **Key storage**: Store private keys securely on the server, using a secure storage mechanism such as a hardware security module (HSM) or encrypted storage. Never expose private keys to the client.
45-
> * **Key usage**: Use the private key only for signing push notification payloads. Ensure that the public key is distributed securely to clients.
46-
>
47-
> For more information on cryptographic best practices, see [Cryptographic Services](/dotnet/standard/security/cryptographic-services).
41+
When implementing push notifications, ensure that cryptographic keys are managed securely:
42+
43+
* **Key generation**: Use a trusted library or tool to generate the public and private keys. Avoid using weak or outdated algorithms.
44+
* **Key storage**: Store private keys securely on the server, using a secure storage mechanism such as a hardware security module (HSM) or encrypted storage. Never expose private keys to the client.
45+
* **Key usage**: Use the private key only for signing push notification payloads. Ensure that the public key is distributed securely to clients.
46+
47+
For more information on cryptographic best practices, see [Cryptographic Services](/dotnet/standard/security/cryptographic-services).
4848

4949
## Create a subscription
5050

0 commit comments

Comments
 (0)