Configure Singpass Application on SDP (In-Progress)
Last updated
Last updated
Every Singpass Application is assigned with a unique identity known as Client ID that will be required when calling Singpass’s Endpoint. Login to to create a new Singpass Application or use an existing application client’s ID for the integration.
Configure the following necessary Application settings.
This application name is the name of your digital service/application. This will appear on the consent page that your users will see when they give consent to login to your digital service.

 Example of consent page when App Name is configured as Test App.
Description of your digital service/application. Describe the use case for your app and what it does for Singpass’s administrative purposes.
A redirect URL is a URL in your application that Singpass will use to redirect users after they have been authenticated or when the ID Token is being returned. For the staging environment, if not set the default callback URL is set to http://localhost:3000 which means users will be redirected to the application's initial loading page.
Provide a JWKS in a JSON format
For configuration with JWKS Endpoint
Select JWKS Endpoint and provide the JWKS Endpoint
For configuration with JWKS Object
Select JWKS Object and provide the JWKS Object
Once saved, the client ID will be populated. This is a unique identity known as that will be required when calling Singpass’s Endpoint.
Set the client profile type. This will determine the from Singpass's token endpoint.
Configure JWKS with the public keys set in the . This will be used by Singpass for verification and encryption purposes. Relying Party (RP) can do so only via ONE of the following forms:
Host the JWKS on a publicly accessible URL. This endpoint must be compatible with
to call Singpass's Authorization Endpoint
If you have successfully integrated with Singpass's Authorization, proceed to
