Client authentication and authorization
Push notification clients are authenticated by the
application server running the NexJ Model Engine
on which the push server is deployed.
Client connections to the push redirector are authenticated through a three-way handshake brokered by the push server. For more information on this process, see Push notification workflow details.
When the push server authenticates a client, the push server generates a unique client ID which acts as a security token that is shared with the push redirector. The push server then redirects the client to the push redirector, passing the client ID as a parameter.