Authentication with Jive Mobile
With Jive 7 and Mobile 3, Jive Mobile apps support OAuth 2 as both an Authorization Server and a Resource Server. This enables several new authentication methods. Basic authentication is no longer supported.
- Authenticating with standard OAuth When you have the Jive for iOS or Jive for Android add-on installed through the Jive Add-ons interface, standard OAuth is the default configuration.
- Authenticating with SAML SSO When your Jive instance is configured with SAML SSO, Jive’s Mobile apps will follow the same authentication flow as the regular web UI.
- Authenticating with activity-based OAuth You can choose to extend users’ OAuth access tokens based on continued activity. By default, users will be required to re-authenticate after 15 minutes of inactivity on the device.
- First-time only authentication with SAML With this method, a user authenticates initially through SAML SSO. Then Jive Mobile converts the session to a longer-lived OAuth session.
- Forced OAuth for mobile only You can enforce OAuth as the authentication method for Mobile users only, even if the instance is configured with SAML SSO.