Corppass
  • INTRODUCTION
    • About Corppass
    • Corppass Design Guidelines
      • Brand Guidelines
      • Button Guidelines
  • Technical Specifications
    • Corppass Authorization API
      • Key concepts
        • Client JWKS
        • JWS and JWE
        • Client Assertion JWT
        • Proof Key of Code Exchange (PKCE)
      • Staging and Production URLs
      • Well-known Endpoints
        • OpenID Discovery Endpoint
        • JWKS Endpoint
      • Scopes
      • Authorization Endpoint
        • Authorization Code with Proof Key of Code Exchange (PKCE) Flow
        • Pushed Authorization Request (PAR) Flow
      • Token Endpoint
        • ID Token Structure
          • UserInfo Claim Structure
          • EntityInfo Claim Structure
        • Access Token Structure
      • Authorization Info Endpoint
        • AuthInfo Structure
        • TPAuthInfo Structure
      • Pushed Authorization Request (PAR) Endpoint
  • Corppass Developer Portal (CDP)
    • User Guide
      • Getting Started
      • Login to CDP
      • Available Digital Service Settings
        • FAQs
      • Toggle Between Staging and Production Environments
      • Portal Features
        • Updating the Digital Service and Managing Metadata
      • User Roles and Permissions
      • Frequently Asked Questions (FAQ)
        • Login Issues
        • Access and Permissions
        • How is CDP Different from Corppass Agency Admin (AA) Portal?
        • Other Common Issues
  • MORE INFORMATION
    • Is Corppass working?
    • Contact Us
Powered by GitBook
On this page
  • Dashboard Overview
  • Digital Service Onboarding
  • Publishing the Digital Service
  1. Corppass Developer Portal (CDP)
  2. User Guide

Portal Features

Dashboard Overview

The Dashboard provides a comprehensive view of all available applications for your entity. From here, you can:

  • View all the apps linked to your entity.

  • Create a new digital service.


Digital Service Onboarding

Follow the steps outlined in the portal to successfully onboard a new digital service. The onboarding process includes:

  1. Creation of a New Digital Service:

    • Enter the required details, such as the service name, description, and metadata.

  2. Approval Process:

    • Once submitted, the service request will be reviewed and approved by GovTech personnel.

    • Once the request is approved, its status will be set to 'Inactive'.

  3. Post-Approval Configuration:

    • After approval, you can configure additional settings:

      • Determine whether the service requires additional checks from the agency.

      • Define which entity types are permitted to use the service.

      • Specify if foreign entities are allowed to transact with the service.

  4. Authorisation Metadata (Optional):

    • You can add the following authorisation metadata to the service:

      • Sub-UEN

      • Roles

      • Parameters

Publishing the Digital Service

  • After completing the onboarding and approval process, you can publish the digital service by clicking the 'Activate' button. This action will change the status of the service to Active, making it available for use.

    • Note:

      If you need to suspend the service for any reason (e.g., security concerns or fraud), you can deactivate it by clicking the 'Deactivate' button. This will change the status of the digital service to 'Inactive', effectively halting its use until it is reactivated.



PreviousToggle Between Staging and Production EnvironmentsNextUpdating the Digital Service and Managing Metadata

Last updated 6 months ago