Tech Documentation for OAuth Changes in Jive 7

Version 1

    Product / Feature name: OAuth 2.0

    Compatible with: Jive Custom 7 and Jive (cloud)

    Release Date: Fall 2013

     

    Overview:

    As of Jive Custom 7 (v7.0.0), Jive now supports OAuth 2.0, acting as both an Authorization Server and a Resource Server. Adding this capability to the Jive platform allows for new integration possibilities, using this open standard.


    OAuth 2.0 provides controlled API access to content in Jive to a third-party service, including a customer-developed internal service or legacy service to which OAuth 2.0 support has been added. In some cases, the access required (see RFC below) to make authorized API requests can simply be between a user accessing Jive through a mobile device or an administrator setting up a webhook to listen for events in a community. Another example is Jive's own integrations, including Jive + Producteev, StreamOnce, and Dealroom (integration with SalesForce), which use OAuth 2.0 to authorize access.

     

    What's Changed / What's New:

    This is an exciting new development, as adoption of this standard has increased significantly among various services.

     

    Technical implications:

    This is primarily targeted at developers of Jive integrations with third party (including internal, etc.) services.

     

    Installation notes:

    The capability is built directly into the Jive v3 API, but does require Jive Custom 7 (v7.0.0) or Jive (cloud) in order to use it. Thus, if you develop a Jive Extension (a.k.a. "Add-on") it is inherently an OAuth client. Depending on your Add-on's requirements, you may use either the Authorization Code Grant or the Resource Owner Password Credentials Grant. Jive does not implement the two other standard grants defined by the specification: Implicit Grant & Client Credentials Grant. Note that in order to use OAuth, you must register a client with Jive.

     

    Notes/FAQ: