Redirect Auth API
The purpose of this guide is to describe the necessary APIs that Relying Parties (RPs) must invoke to facilitate an Open ID Connect (OIDC) authentication for a Singpass user via the Redirect Authentication Flow.
Refer to this diagram for an overview of the Redirect Authentication Flow between RP, Singpass, and other dependencies.
RPs are to implement the following steps referenced in the Redirect Authentication Flow diagram above:
Frontend:
Step 1a: Redirect to Authorization endpoint
Backend:
Step 4: Exchange auth code with ID token (involves client authentication) using Token endpoint
Last updated
