OneSpan.SamBakken

Action Before March 31: Upgrade .NET Server-Side Notification SDK for Apple Push Notification Compliance

0 votes

Please remember that Apple set a March 31, 2021 deadline to upgrade to the Apple Push Notification service (APNs) API provider (see: https://developer.apple.com/news/?id=c88acm2b). After March 31, push notifications can no longer be sent to iOS apps using the legacy binary protocol because Apple will no longer support it. 

This impacts your use of Server-Side Notification SDKs in combination with OneSpan Mobile Authenticator Studio (MAS) and/or Mobile Security Suite (MSS) for the sending of push notifications to iOS apps. Past release notifications have explained this new requirement, and this message serves as a final notification of the action required of customers to ensure uninterrupted sending of push notifications to iOS apps. 

To ensure uninterrupted sending of push notifications to your MAS or MSS app for iOS, you need to at a minimum use or upgrade to one of the following Server-Side Notification SDK versions by March 31, 2021

Server Notification SDK Minimum Versions for APNs Compliance 

  • .NET Server-Side Notification SDK version 4.25.2 

Where/How to Upgrade 

For customers with a valid maintenance contract, current MAS and MSS releases are available for download from the OneSpan Customer Portal. If you have additional questions, please contact OneSpan support at [email protected]

Sam Bakken
OneSpan
Director of Product Marketing | Mobile and Identity Solutions


Reply to: Action Before March 31: Upgrade .NET Server-Side Notification SDK for Apple Push Notification Compliance

0 votes

The HTTP/2-based Apple Push Notification service (APNs) provider API lets you take advantage of great features, such as authentication with a JSON Web Token, improved error messaging, and per-notification feedback. If you still send push notifications with the legacy binary protocol, make sure to upgrade to the APNs provider API as soon as possible. APNs will no longer support the legacy binary protocol after March 31, 2021.

indigocard


Reply to: Action Before March 31: Upgrade .NET Server-Side Notification SDK for Apple Push Notification Compliance

0 votes

Upon receiving your server’s POST request, APNs validates the request using either the provided authentication token or your server’s certificate. If validation succeeds, APNs uses the provided device token to identify the user’s device. It then tries to send your JSON payload to that device.

 

sky light pay card

 


Reply to: Action Before March 31: Upgrade .NET Server-Side Notification SDK for Apple Push Notification Compliance

0 votes

Use .NET Core/5+ for your server application when:

  • You have cross-platform needs.
  • You're targeting microservices.
  • You're using Docker containers.
  • You need high-performance and scalable systems.
  • You need side-by-side .NET versions per application.

MCDVOICE

Use .NET Framework for your server application when:

  • Your app currently uses .NET Framework (recommendation is to extend instead of migrating).
  • Your app uses third-party .NET libraries or NuGet packages not available for .NET Core/5+.
  • Your app uses .NET Framework technologies that aren't available for .NET Core/5+.
  • Your app uses a platform that doesn't support .NET Core/5+.

Reply to: Action Before March 31: Upgrade .NET Server-Side Notification SDK for Apple Push Notification Compliance

0 votes

Upon receiving your server’s POST request, APNs validates the request using either the provided authentication token or your server’s certificate. If validation succeeds, APNs uses the provided device token to identify the user’s device. It then tries to send your JSON payload to that device.

Target Pay and Benefits


Hello! Looks like you're enjoying the discussion, but haven't signed up for an account.

When you create an account, we remember exactly what you've read, so you always come right back where you left off