Version 2


    Jive 7.0 incorporates Mobile 3, which results in a number of important changes to mobile access.


    This document is intended to help Jive 4.5, Jive 5, or Jive 6 customers who are planning an upgrade to Jive 7.0 understand the changes in mobile access that are part of this upgrade.


    What is Mobile 3?

    The table below describes the components of Mobile 3 compared to the previous Mobile 2 architecture.


    Mobile 3Mobile 2
    Compatible Jive Versions

    Jive 6, Jive 7, Jive Cloud

    Jive 4.5.6+, Jive 5, Jive 6

    Mobile Admin Plugin

    integrated with Jive 7 installation

    separate download & install

    Mobile Web*

    (mobile-specific web interface)

    integrated with main Jive server as part of Mobile Admin Plugin; mobile browsers connect to <Jive URL>/mobile/

    served from Jive Mobile Gateway; mobile browsers connect to <mobile hostname>

    Native iOS App

    Jive 3.0 for iOS - runs on both iPhone & iPad

    Jive Mobile 2.x for iPhone - iPhone only

    Native Android App

    Jive 3.0 for Android - not yet released

    Jive Mobile 1.x for Android

    * Mobile Web refers to the mobile-specific web interface enabled by the mobile module.  It does not refer to using the full Jive web interface from a mobile browser.  Support for accessing the full Jive web interface from mobile browsers depends on the Jive version, not on the Mobile module version.


    Notable Changes

    The following changes to mobile access should be expected when upgrading to Jive 7.0.  This does not include many of the user-visible feature changes, as this document is intended to highlight only the most significant changes to mobile access that are relevant to planning an upgrade.  For a more detailed list of feature differences, please refer to Jive Mobile Product Comparison Matrix | Jive Community.


    iOS Support

    Native App

    • Jive 7.0 is compatible with the new Jive 3.0 iOS app, but not with the Jive Mobile 2.x iPhone app.  Jive Mobile 2.x app users will be prompted to install the Jive 3.0 app when they use the older 2.x app to connect to a Jive 7 community.
    • Jive 3.0 for iOS requires iOS 6.0.1 or later.
    • For more information on the Jive 3.0 iOS app, please see Jive 3.0 iOS App (Mobile 3): Technical Note | Jive Community and the Jive documentation

    Mobile Web

    • Mobile Web in Jive 7.0 supports access from iOS 6.0 or later on iPhones using Mobile Safari
    • Mobile Web for iPad is no longer available -- this refers to the iPad-specific web interface, not to using the full web UI on an iPad
    • Jive 7.0  supports access to the full web UI directly from Mobile Safari on iPads and iPhones running iOS 6.0 later.


    Android Support

    Native App

    • The Jive Mobile 1.0.x app for Android is not supported with Jive 7.0.
    • A new, redesigned native app for Android is under active development, with planned availability in Q2 of 2014.  We recommend mobile web as an interim solution for Android users.

    Mobile Web

    • Mobile Web in Jive 7.0 supports access from Android 2.3 or later devices using the standard Android web browser


    Jive Mobile Gateway

    The Jive Mobile Gateway no longer proxies all incoming traffic for from web browsers or native apps.

    • Mobile devices must be able to access the Jive instance and any required SAML SSO page (IdP) directly, which may require using a VPN, MDM, or other proxy.
    • Mobile Web was previously served from; with Jive 7.0 it is now served directly on the Jive instance at <Jive URL>/mobile/
    • Web browsers that attempt to access your previous Mobile Web URL at <hostname> will be redirected to the Jive URL

    The Mobile Gateway is still used as a push notification gateway for the standard distributions of Jive native apps.


    Authentication Changes

    • Mobile Web and the Jive 3.0 iOS app use the same web-based SAML SSO that desktop users would use to access Jive, if any is configured.  Note that the sign-in page (IdP) must be accessible directly from the mobile device, or a VPN, MDM or other proxy may be required.
    • If no SSO is configured, username/password authentication will be used instead.
    • Mobile device registration/activation and mobile passcode are not available with Jive 7.  We recommend using an MDM solution for greater device-level security.

    More details on the security of Mobile 3 are available here:


    Custom Enterprise iOS App Distribution and MDM Wrapping

    With Mobile 3, we are introducing a program to enable custom enterprise distribution of the iOS app, including wrapping with MDM tools like Good Dynamics or MobileIron. Participating customers will be provided access to iOS binaries (.ipa files) for the Jive app, and will be able to perform some customizations, as well as app signing and wrapping. Contact your Jive account representative for more information.


    Jive Present

    The Jive Present plugin is now separate from the Jive Mobile Admin plugin.  Data from any existing installation of Jive Present will be upgraded to be used by the new Jive Present plugin. The only difference is that administrators will see Jive Present as a separate plugin in the Plugins section of the Admin Console.  No changes will be visible to end users of Jive Present.


    On-Premise Mobile Plugin

    No separate "on-premise" plugin will be released for Jive 7.0.  The way mobile access works with Jive 7.0 already meets the architectural requirements that were being satisfied by the separate on-prem plugin for Jive 6.0.  Specifically:

    • API traffic is not proxied through the Jive Mobile Gateway
    • Mobile Web authenticates using the same system (e.g., SSO) as desktop users

    Please take note of the following significant changes between the previous on-prem mobile plugin and version 6.1:

    • Mobile Web for iPad is no longer available -- this refers to the iPad-specific web interface, not to using the full web UI on an iPad
    • Native app access, which was not available with Jive 6 + On-Prem Mobile, is now possible from the Jive 3.0 app for iOS
      • The standard app available from the App Store sends push notifications through the Jive Mobile Gateway.  However, push notifications can be disabled, or you can opt for custom enterprise distribution (see above), which will allow push notifications to be sent directly to Apple's push servers using your enterprise certificate.




    Can we continue to use the Mobile 2 module with Jive 7.0?

    No, only the Mobile 3 module is compatible with Jive 7.0.


    Our web SSO/policies is not designed to work with mobile devices, are there any alternatives?

    Not right now, but we are working on more authentication options for a future release of Jive 7.  Please stay tuned.