We are thrilled to announce the introduction of VAPID (Voluntary Application Server Identification) for Web Push, making the configuration of WPN (Web Push Notifications) easier than ever before. With VAPID, you no longer need to deal with the complexities of FCM (Firebase Cloud Messaging) setup.

Simplified VAPID Configuration: Under the Push Notifications settings section in Assets → Websites, you'll now find an option to enable VAPID. If you already have VAPID keys, simply input the Public Key and Private Key in the provided fields.

Generating VAPID Keys: For those who don't have VAPID keys yet, worry not! We've made it easy. Just inform your onboarding manager at Netcore and we will create the VAPID keys for you.

Seamless JS Integration: On the JS side, we've made the integration seamless. The service worker will utilize the VAPID public key to generate push tokens and sync with Netcore's backend.

Smooth Transition from VAPID to VAPID: Moving from VAPID implementation of another vendor to VAPID in Netcore is hassle-free. We will take care of re-subscribing users with legacy tokens, smoothly transitioning them to VAPID. No permission pop-up will reappear, ensuring a seamless experience.

Interested in knowing more about what VAPID is?

VAPID is a security layer for Web Push subscriptions, ensuring that only authorized parties with the VAPID private key can use the subscriptions. It is defined by RFC 8292 and has become a separate standard to enhance the security of Web Push. Refer to this link for more information - https://developer.chrome.com/blog/web-push-interop-wins/#introducing-vapid-for-server-identification

Documentation