> For the complete documentation index, see [llms.txt](https://docs.corppass.gov.sg/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.corppass.gov.sg/corppass-developer-portal-cdp/user-guide/portal-features/digital-service-configuration.md).

# Digital Service Configuration

Before initiating the configuration of your digital service for Corppass Login in the Corppass Developer Portal (CDP), ensure that the following details are gathered. This preparation will help streamline the setup process and ensure alignment with your organisation’s requirements.

### 1. OIDC Parameters

* **Callback URL**:
  * The URL where your digital service will receive responses from Corppass after authentication.
  * Multiple callback URLs can be associated with each service if required.
  * Ensure that these URLs are registered correctly and accessible by your application.
* **JWKS Endpoint or Object**:
  * JWKS provides a secure method to share public keys for verifying JSON Web Tokens (JWTs).
  * This must contain both signing keys (for Client Assertion / DPoP) and encryption keys (for ID Tokens).
  * Each digital service is linked to a unique Client ID, meaning only one JWKS endpoint or object is permitted per service.
  * The endpoint must be securely hosted and accessible by Corppass for token verification.

### 2. [Entity Types](/corppass-developer-portal-cdp/user-guide/faq/digital-services.md#what-are-the-allowed-entity-types-for-a-digital-service)

Consider the types of entities that will be authorised to access and transact using your digital service. 

### 3. [Entity Statuses](/corppass-developer-portal-cdp/user-guide/faq/digital-services.md#what-are-the-allowed-entity-statuses-for-a-digital-service)

Identify the statuses that your digital service will permit.

### 4. Third-Party Transactions

Decide whether the digital service will allow third-party entities to transact on behalf of their clients.

### 5. Foreign Entities

Determine whether the digital service will support transactions by foreign entities.

### 6. Additional Parameters

If applicable, prepare any additional details required for the digital service. 

* **Sub-UEN**: Sub-entity identifiers for more granular access control.
* **Roles**: Role definitions for assigning specific user permissions.
* **Custom Parameters**: Any other custom parameters relevant to the service.

{% hint style="warning" %}
Please note that some of these configurations cannot be modified after a digital service is published. Refer to this [section](/corppass-developer-portal-cdp/user-guide/faq/digital-services.md#what-settings-cannot-be-changed-after-publishing-the-digital-service) for more details.
{% endhint %}

### 7. Test the Service in the Staging Environment

Before proceeding to the production environment, it is essential to test the service in the Staging environment. This ensures:

* The configurations are functioning correctly.
* Security and authentication protocols are working as expected.
* Integration tests are conducted to resolve any potential issues.

### 8. Create Digital Service in the Production environment and update Billing Information

After the digital service has been fully configured and tested in the Staging environment, create the service in the Production environment. The status will be set to **"Reviewing."** Please provide your billing details at this stage.

Once the billing details are submitted, the Corppass team will review and approve the service. The status will then change to **"Inactive."** The RP can decide when to activate the service after completing the necessary configuration.

Note: You are not required to upload the approval email, as having a Corppass account with the 'admin' role to the 'Corppass Developer Portal' (CDP) service confirms your eligibility to onboard and publish a service.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.corppass.gov.sg/corppass-developer-portal-cdp/user-guide/portal-features/digital-service-configuration.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.