Re:HTTP/2 Protocol for iOS Push Notifications
by simscitizen on Thursday February 25, 2016 @03:11PM
(#11177415)
Because it's fundamentally different and more secure.
Apple's model uses a public/private key pair: the private key never leaves your server and Apple doesn't know it. Apple only knows the public key, in the form of a cert. Apple actually writes about the trust model in the docs: https://developer.apple.com/library/ios/documentation/Networ....
Google's model uses a shared secret (the API key) that both the client and server know.
Having worked with both systems, I prefer the ease of the shared secret model, but each system uses a fundamentally different security model.
Re:HTTP/2 Protocol for iOS Push Notifications
by alexbilbie on Thursday February 25, 2016 @01:23PM
(#11176478)
Just a guess but once you've completed the TLS negotiation the APNS server doesn't need to re-authenticate for the lifetime of the socket connection whereas with API keys the key would need to be verified with each notification (because a new connection would be created)?
Re:HTTP/2 Protocol for iOS Push Notifications
by jamieb007 on Thursday February 25, 2016 @02:50PM
(#11177250)
There must be a worthwhile reason - the added complexity of certs is non-trivial [1]. Perhaps certs are deemed less easily transferable compared to API keys (simple strings)?
[1] https://developer.apple.com/library/ios/documentation/IDEs/C...
Re:HTTP/2 Protocol for iOS Push Notifications
by sbose78 on Thursday February 25, 2016 @01:21PM
(#11176449)
It helps the APNS server identify the sender server better since the certificate does have more details.
Also, having the certificate helps in signing and encrypting the notification packets triggered from the server.
Does anyone know why Apple uses certificates instead of API keys (a la GCM) for authorization?