Determining Pivotal Single Sign‑On App Type
Warning: Pivotal Single Sign-On v1.11 is no longer supported because it has reached the End of General Support (EOGS) phase as defined by the Support Lifecycle Policy. To stay up to date with the latest software and security updates, upgrade to a supported version.
This topic explains how to determine your Pivotal Single Sign‑On app type.
Before you bind or register an app, you must determine its Single Sign‑On app type and the corresponding OAuth grant type. OAuth grant types determine how the app communicates with Single Sign‑On to acquire tokens for authentication and authorization purposes.
See the table below to determine your app’s Single Sign‑On app type and OAuth Grant Type:
|App Type||Single Sign‑On App Type||OAuth Grant Type|
|Web||Web App||Authorization Code|
|Native Mobile, Desktop, or Command Line||Native App||Resource Owner Password|
|Service-to-Service||Service-to-Service App||Client Credentials|
|Web + Service-to-Service||Web + Service-to-Service App||Authorization Code and Client Credentials|
|Resource Server||Secured API, Database Server||n/a|
The Single Sign‑On Service Sample Applications GitHub repository provides examples for a few of the 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.