Determining Pivotal Single Sign‑On App Type

This topic explains how to determine your Pivotal Single Sign‑On app type.

Determine Your Pivotal Single Sign‑On App Type

Before you bind or register an app, you must determine its Pivotal Single Sign‑On app type and the corresponding OAuth grant type. OAuth grant types determine how the app communicates with Pivotal Single Sign‑On to acquire tokens for authentication and authorization purposes.

If your app authenticates end users, its Pivotal Single Sign‑On app type is Web App, Native App, or Single-Page JavaScript App. If the app does not authenticate end users, but rather accesses other services or APIs on its own behalf, then its type is Service-to-Service App.

See the table below to determine your app’s Pivotal Single Sign‑On app type and OAuth Grant Type:

App Type Pivotal Single Sign‑On App Type OAuth Grant Type
Web Web App authorization code
Native Mobile, Desktop, or Command Line Native App password (the resource owner’s password)
Single-Page JavaScript Single-Page JavaScript App implicit
Service-to-Service Service-to-Service App client_credentials
Web + Service-to-Service Web + Service-to-Service App authorization_code client_credentials
Resource Server Secured API, Database Server n/a

The Pivotal Single Sign‑On Service Sample Applications GitHub repository provides examples for a few of the Pivotal Single Sign‑On app types listed above.

Note Pivotal recommends only using the Native app type for highly-trusted apps, such as company-owned and managed apps. The Native app type only works with back-channel protocols, such as internal UAA store or LDAP. It does not work with front-channel protocols, such as SAML.