-
-
Notifications
You must be signed in to change notification settings - Fork 67
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Certificate Authority (CA) for Apple Push Notification (APN) is changing #161
Comments
Thanks for opening this issue! |
Thanks for opening this issue. I'm wondering about it too. |
I don't think we hardcode any CAs here. Trust stores are managed by the environment in which this library runs. In fact, if you look at the docs, there is an option
In well managed environments, where trust stores are automatically updated, like in the latest server instance images of popular cloud service providers, there should be no action necessary. If you self-manage your trust store, or run on an old or unmaintained OS image, you'd either have to invoke a trust store update, or download the new CA certificate and manually add it to the trust store. If you are unsure, you have 1 month from when the APNS sandbox environment won't work anymore (January 20, 2025) to when the APNS production environment won't work anymore (February 24, 2025). Use that time to verify whether any action is required on your side. |
Thanks for taking time to explain the situation @mtrezza! |
It says in the docs that Thanks! |
FYI, I have tested node-apn following the update to the server certificates in sandbox on January 20, 2025, and everything works as before. |
It is working for me as well 🙂 |
I wasn't sure where to post this - but was trying to figure out if uses of this library need to take any action in response to Apple announcement that APNs will update the server certificates in early 2025?
https://developer.apple.com/news/?id=09za8wzy
The text was updated successfully, but these errors were encountered: