Closed natanrolnik closed 7 years ago
@EricNetsch I was planning to do this but I wasn't sure about the implementation. The dependency used here, APN, already supports using APNS authentication tokens. But it's a major update on their package, that has some breaking changes to the one currently used here.
@natanrolnik Ok, got it. It definitely adds some complexity to the token management and would require a cache per "defaultTopic" or bundle Id. This feature is critical for one of our projects which supports multiple iOS applications on one parse-server (multiple bundle ID's). Please keep me updated and let me know how I can help
@EricNetsch if I remember correctly, you already can send push to multiple applications with different bundle ids in the current versions. Take a look here, and check how you can pass an array of configurations.
I would also love to see this supported.
@NatanRolnik that's not good solution. We need to be able to support dynamic bundle ID's without re-deploying the server code every time we have a new app. Using the tokenized method is the right solution
@EricNetsch if I remember correctly, the module apn also requires the bundle id, otherwise it's not able to package the JWT. I might be wrong, but if that's the case, it would need re-deploying anyway.
Yes, it does require a bundle ID to create a token. The idea is that you could pass it the bundle ID (dynamically) to create the token. All bundle ID's will work if they share the same Team Identifier. This would allow us to create tokens for new apps without having to re-deploy/update the server code. The bundle ID could be passed as a parameter when creating a token.
There is a PR open that enables support for APNS Auth Token. You can look at it here: #52
However, @EricNetsch, the current implementation on that PR does require a deploy in order to add/remove bundle IDs.
@natanrolnik with the release of v2.0.0 that features APNS v2 is that issue still relevant?
🙏🏻🎉
(Issue originally opened by @EricNetsch in ParsePlatform/parse-server#3315)
I would like to start using Apple's new push notification authentication protocol instead of using traditional certs. Is this possible with parse-server yet? This would be a fantastic addition to the platform to simplify push certificate management.
https://developer.apple.com/library/content/documentation/NetworkingInternet/Conceptual/RemoteNotificationsPG/CommunicatingwithAPNs.html
Please advise on any existing solutions/ implementations.