-
-
Firebase Cloud Messaging
-
This content has been machine translated dynamically.
Dieser Inhalt ist eine maschinelle Übersetzung, die dynamisch erstellt wurde. (Haftungsausschluss)
Cet article a été traduit automatiquement de manière dynamique. (Clause de non responsabilité)
Este artículo lo ha traducido una máquina de forma dinámica. (Aviso legal)
此内容已经过机器动态翻译。 放弃
このコンテンツは動的に機械翻訳されています。免責事項
이 콘텐츠는 동적으로 기계 번역되었습니다. 책임 부인
Este texto foi traduzido automaticamente. (Aviso legal)
Questo contenuto è stato tradotto dinamicamente con traduzione automatica.(Esclusione di responsabilità))
This article has been machine translated.
Dieser Artikel wurde maschinell übersetzt. (Haftungsausschluss)
Ce article a été traduit automatiquement. (Clause de non responsabilité)
Este artículo ha sido traducido automáticamente. (Aviso legal)
この記事は機械翻訳されています.免責事項
이 기사는 기계 번역되었습니다.책임 부인
Este artigo foi traduzido automaticamente.(Aviso legal)
这篇文章已经过机器翻译.放弃
Questo articolo è stato tradotto automaticamente.(Esclusione di responsabilità))
Translation failed!
Firebase Cloud Messaging
Note:
Firebase Cloud Messaging (FCM) was previously known as Google Cloud Messaging (GCM). Some XenMobile console labels and messages use the GCM terminology.
Citrix recommends that you use Firebase Cloud Messaging (FCM) to control how and when Android devices connect to XenMobile. XenMobile, when configured for FCM, sends connection notifications to Android devices that are enabled for FCM. Any security action or deploy command triggers a push notification to prompt the user to reconnect to the XenMobile server.
After you complete the configuration steps in this article and a device checks in, the device registers with the FCM service in XenMobile Server. That connection enables near real-time communication from your XenMobile service to your device by using FCM. FCM registration works for new device enrollments and previously enrolled devices.
When XenMobile needs to initiate a connection to the device, it connects to the FCM service. Then, the FCM service notifies the device to connect. This type of connection is similar to what Apple uses for its Push Notification Service.
Prerequisites
- Latest Secure Hub client
- Google developer account credentials
- Google Play services installed on FCM-enabled Android devices
Firewall ports
- Open port 443 on XenMobile to
fcm.googleapis.com
andGoogle.com
. - Open outgoing, Internet communication for device Wi-Fi on ports 5228, 5229, and 5230.
- To allow outgoing connections, FCM recommends allowing ports 5228 through 5230 with no IP restrictions. However, if you require IP restrictions, FCM recommends allowing all the IP addresses in the IPv4 and IPv6 blocks. Those blocks are listed in the Google ASN of 15169. Update that list monthly. For more information about FCM ports, see the Google documentation on FCM ports.
For more information, see Port requirements.
Architecture
This diagram shows the communication flow for FCM in the external and internal network.
To configure your Google account for FCM
-
Sign in to the following URL using your Google developer account credentials:
-
Click Add project.
-
After you create the project, click Project settings.
-
Click the Cloud Messaging tab.
-
If the Cloud Messaging API (Legacy) is disabled, then the Server key is not be displayed.
Enable the Cloud Messaging API (Legacy) as follows:
-
Click the Ellipses button next to Cloud Messaging API (Legacy) and then click Manage API in Google Cloud Console.
-
Under CLoud Messaging, click Enable button.
-
-
Copy the Server key and Sender ID values. In the next procedure, you paste those values in the XenMobile console. As of October 2016, you must create Server Keys in the Firebase console.
For steps to set up an FCM client app on Android, see this Google Developers Cloud Messaging article: https://firebase.google.com/docs/cloud-messaging/android/client.
To configure XenMobile for FCM
In the XenMobile console, go to Settings > Firebase Cloud Messaging.
-
Edit API key, and type the Firebase Cloud Messaging Server key that you copied in the last step of Firebase Cloud Messaging configuration.
-
Edit Sender ID, and type the Sender ID value you copied in the previous procedure.
After you complete the setup, you can remove your Scheduling device policy or change that policy to connect less often.
To test your configuration
-
Enroll an Android device.
-
Leave the device idle for some time, so that it disconnects from XenMobile.
-
Sign in to the XenMobile console, click Manage, select the Android device, and then click Secure.
-
Under Device Actions, click Selective Wipe.
In a successful configuration, selective wipe occurs on the device.
Share
Share
This Preview product documentation is Citrix Confidential.
You agree to hold this documentation confidential pursuant to the terms of your Citrix Beta/Tech Preview Agreement.
The development, release and timing of any features or functionality described in the Preview documentation remains at our sole discretion and are subject to change without notice or consultation.
The documentation is for informational purposes only and is not a commitment, promise or legal obligation to deliver any material, code or functionality and should not be relied upon in making Citrix product purchase decisions.
If you do not agree, select Do Not Agree to exit.