Vendor Push Platform | Configuring in the IM console |
| Note: Specified in-app page link cannot be modified. This configuration is for dispatching event listening for the offline push plugin after a click; direct configuration of in-app page navigation is not allowed. |
Vendor Push Platform | Configuring in the IM console |
| Note: Client ID corresponds to AppID, Client Secret corresponds to AppSecret. Specified in-app page link cannot be modified. This configuration is for dispatching event listening for the offline push plugin after a click; direct configuration of in-app page navigation is not allowed. |
Vendor Push Platform | Configuring in the IM console |
| Note: Specify In-App Interface Link, cannot be modified. This configuration is for event listening of the offline push plugin after a click, direct configuration of in-app page redirect is not allowed. |
Vendor Push Platform | Configuring in the IM console |
| Note: Specified in-app page link cannot be modified. This configuration is for dispatching event listening for the offline push plugin after a click; direct configuration of in-app page navigation is not allowed. |
Vendor Push Platform | Configuring in the IM console |
| Note: Specified in-app page link cannot be modified. This configuration is for dispatching event listening for the offline push plugin after a click; direct configuration of in-app page navigation is not allowed. |
Vendor Push Platform | Configuring in the IM console |
| Note: Specified in-app page link cannot be modified. This configuration is for dispatching event listening for the offline push plugin after a click; direct configuration of in-app page navigation is not allowed. |
| Certificate Type | Validity Period and Management | Security | Dynamic Island |
P12 Certificate | A P12 certificate is a binary file that contains both a public and a private key, used for certificate-based authentication. It bundles the public key certificate and the private key into one file, with an extension of .p12 or .pfx. | P12 certificates usually have a validity period of one year, after which they need to be regenerated and deployed. Each application requires a separate P12 certificate to handle push notifications. | Certificate: The P12 certificate uses certificate-based authentication, requiring the private key to be stored on the server. This may increase the security risk, as the private key could be accessed by unauthorized users. | Not supported |
P8 Certificate | A P8 certificate is an Authorization Key, used for token-based authentication. It is a text file containing a private key, with an extension of .p8. | P8 certificates do not have an expiration date, so you do not need to worry about certificate expiration. Moreover, using a P8 certificate can simplify certificate management, as you can use one P8 certificate to provide push notification services for multiple applications. | P8 certificates use token-based authentication, meaning your server periodically generates a JSON Web Token (JWT) to establish a connection with APNs. This method is more secure, as it does not require storing a private key on the server. | Supports Dynamic Island Push |
Push Notification
Service
to your existing AppID.Bundle ID
cannot use the wildcard *
, otherwise, the remote push service cannot be used.Bundle ID
and other information, click Continue to proceed to the next step.SSL Certificates
for the development environment (Development) and the production environment (Production), as shown below:Keychain Access - Certificate Assistant - Request a Certificate From a Certificate Authority
).*.certSigningRequest
file.*.certSigningRequest
file.Development SSL Certificate
to your local environment.Production SSL Certificate
for the production environment to your local machine.SSL Certificate
for the development and production environments. The system will import it into the keychain.Apple Development IOS Push Services
and Apple Push Services
for the development and production environments as p12
files respectively..p12
file.
Was this page helpful?