Native apps and push notifications
You can use the Native Apps settings to disable push notifications if you don't want to use them. Or, if you have a custom distribution of the native app, you can configure Jive to use an Apple or Android certificate to send push notifications.
Admin Console: Mobile
Push notification defaults
By default, push notifications are on and are relayed through the Jive Push Service. If you want to shut them off, click None - disable push notifications.
Push notifications continue to send data through the Jive Push Service securely via HTTPS, but do not require authentication. To ensure Jive can send push notifications, you'll need to enable outbound traffic from your Jive instance to the following IP address on port 443:
- 204.93.84.65
Due to iOS and Android security restrictions on which credentials are needed to push to an application, push notifications must go through Jive's push notification gateway to reach the standard Jive Mobile application. If you don't like this behavior, you can disable push notifications, or you can do a custom app distribution and configure custom push directly through Google's and Apple's servers, as described below.
Custom push notifications
Custom push notifications go directly from the Jive server to the appropriate notification services (GCM from Android and APNS for iOS). For security, Android and iOS require that the credentials used to send push notifications to an app match the credentials used to sign the distributed app. Therefore, to use custom push notifications, you must have a customized version of the app that is signed by your organization's appropriate credentials. You can upload your organization's APNS credentials and/or GCM key on the Mobile page of the Admin Console.