Hello,
Our setup is as follows:
- We have one app and we’re using APNS authentication to wake up customer devices.
- We’ve got various provider servers running, and communicating with Apple.
- Over the course of the next few months, these servers will be updating:
- From the old binary API for sending notifications to APNs (using certificate authentication).
- To the new HTTP/2 based API for sending notification to APNs (continuing to use certificate authentication).
- And then gradually to using Token-Based authentication with the new API.
Therefore over the course of the next year we are likely to have a number of systems, supporting the same App, using all three mechanisms specified above. This relies on a few assumptions about the behaviour of the Apples servers, namely:
- Apple support copes with this eventuality – i.e. the fact that one server is sending notifications using certificate-based authentication doesn’t affect the ability of another server to send notifications using token-based authentication.
- If due to installation problems, a Key ID is mis-typed on one provider server, then that provider server will lose the ability to post notifications until the correct password is supplied - i.e. Apple will correctly fail to authenticate it. However, we are assuming that this will affect the single provider server only, and not other provider servers which are using the same token, but have supplied the correct Key ID.
Are these assumptions valid? In other words, is the Trusted Connection to APNs from each provider server independent? And failure of one provider server, or choice of authentication method used by one provider server, will have no impact on other provider servers and their ability to send remote notifications through APNs for the same app.
Thanks.