Configuring API clients
Faspex requires your application use OAuth 2 to authorize your application to access protected Faspex resources.
OAuth 2 methods
Before your application can authorize to Faspex using OAuth 2, you must first register an API
client for your application. Faspex supports these OAuth 2 methods:
- OAuth 2 with SAML
- Web applications requiring users to authenticated through a configured SAML identity provider (SAML IdP). For details, see Working with SAML.
- OAuth 2 PKCE (Proof Key for Code Exchange)
- Web and mobile applications requiring users to enter credentials into a user login page, which
then authenticates to the Faspex server. For details, see Configuring OAuth 2 for user-based workflows.Note: The Faspex UI acts as an OAuth 2 client to authenticate to the Faspex API server. The Faspex UI is a pre-registered OAuth 2 client.
- OAuth 2 JWT (JSON Web Token Grant)
- Non-web applications that do not require access to user-protected endpoints, such as an application that monitors background jobs. For details, see Configuring OAuth 2 for non-user-based workflows (JWT).
To register an OAuth 2 client: