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
  • Updating the Digital Service
  • Managing Metadata
  • Note:
  1. Corppass Developer Portal (CDP)
  2. User Guide
  3. Portal Features

Updating the Digital Service and Managing Metadata

The Corppass Developer Portal allows you to manage the metadata associated with your digital services, ensuring that your services remain up-to-date and accurate. This includes the ability to add, update, or delete metadata entries related to your digital service.

Updating the Digital Service

You can update the details of an existing digital service at any time. This includes:

  • Service Name

  • Description

  • Metadata

Updates to these fields can be made directly in the portal and do not require additional approval. The agency admin is responsible for managing any changes to the digital service data.

Managing Metadata

The portal also allows you to manage the metadata linked to your digital services. This includes:

  • the OIDC Parameters

  • advanced settings

  • authorisation metadata

Note:

Once a digital service is published and in an 'Active' state, certain configurations cannot be modified as entity users' explicit authorizations are tied to them:

  • UEN Entity Types: Once allowed, they cannot be removed.

  • Parameters: Once published, they cannot be added, edited, or removed.

  • Roles: Once published, they cannot be added, edited, or removed.

Ensure all configurations are carefully reviewed before publishing.

PreviousPortal FeaturesNextUser Roles and Permissions

Last updated 6 months ago