> For the complete documentation index, see [llms.txt](https://docs.catalyx.solutions/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.catalyx.solutions/catalyx-package-manager/registration-guide.md).

# Registration Guide

***

## Overview of the Required Steps

1. **Provide Corporate Data** – Provide your organisation’s basic company details.
2. **Authenticate your Organisation** – Provide your company's OpenID Connect (OIDC) details.
3. **Log in to your Canton Node** – Log in to your Canton validator node and install the CPM DAR file to complete the installation.

{% hint style="success" %}
**CPM never stores or receives your credentials.**

When you register, the CPM web application runs entirely in your browser. Your OIDC credentials, node authentication tokens, and any other sensitive details are communicated directly between your browser and your own infrastructure — they never pass through IntellectEU's servers.

CPM does not create user accounts on its own systems. Authentication is handled exclusively by your organisation's own identity provider (OIDC). The only information stored on the CPM side is what you explicitly provide during registration (company details, OIDC issuer URL, Canton Party ID), which is recorded on the Canton Ledger as a join request.

This was a deliberate design goal: **your credentials stay on your side.**
{% endhint %}

***

## Step-by-Step Instructions

Please follow the instructions carefully. If at any point you need assistance, please contact our support: <catalyst-support@intellecteu.com>

To begin the onboarding process, you must first navigate to the CPM platform at [https://apps.catalyx.solutions](https://apps.catalyx.solutions/marketplace) and click the **Sign Up** button in the top right corner of the screen.

{% stepper %}
{% step %}
**Provide Corporate Data**

In this step, you will provide the necessary information about your organisation. All fields are mandatory to proceed.

* **Company Legal Name** - Enter your full legal company name as registered in your jurisdiction.
* **Tax ID / Company ID** - Provide your official tax identification number or company registration number.
* **Registered Address** - Enter the full registered address of your organization.
* **Full Name** - Provide your full name as the primary contact person completing the onboarding.
* **Email** - Enter your business email address. This will be used for all communication related to the platform.

Once all fields are filled in, click **Next Step** to continue to step 2.

<figure><img src="/files/bRsadeYYO0Tp2oJ6rJeX" alt=""><figcaption></figcaption></figure>
{% endstep %}

{% step %}
**Authenticate your Organisation**

Next, you will provide your organisation’s OpenID Connect (OIDC) details. These are used to securely authenticate your organisation.

* **OIDC Client ID** - Enter the client ID assigned to your organisation.
* **OIDC Issuer URL** - Provide the URL of your OIDC identity provider (Issuer).

Once all fields are filled in, click **Next Step** to proceed to Step 3.

<figure><img src="/files/succYcF9liJLm0DwiXjN" alt=""><figcaption></figcaption></figure>
{% endstep %}

{% step %}
**Log in to your Canton Node**

After completing Step 3, you will be prompted to log in to your Canton validator node. This confirms your ownership and access to the infrastructure.

Once logged in, you will need to provide your node information and download the CPM DAR file to complete the installation.

![Node Setup](/files/TlYmCQvL3wgbDGGynld4)

**Section 1: Node Information**

* **Company Domain** - `<your official web domain>` - this domain will be used to log in to the CPM platform after registration.
* **Canton Party ID** - Used for invoicing purposes and identification within the Canton network. Enter the Party ID associated with your validator node.
* **JSON Ledger API URL** - Provide the URL used to access your node’s Ledger API.

<figure><img src="/files/6f4Xyh3EopC7I0DMoa3A" alt=""><figcaption></figcaption></figure>

{% hint style="warning" %}
Configuring CORS for JSON Ledger API access is mandatory

To allow the CPM user interface to communicate with your Canton validator node, you must configure **Cross-Origin Resource Sharing (CORS)** on your JSON Ledger API.

Ensure that your JSON Ledger API is configured to allow requests from the CPM UI origin, including the required HTTP methods and headers.

CPM UI Origin to be used:

1. MainNet - apps.catalyx.solutions
2. TestNet - TBA
3. DevNet - TBA

At a minimum, your CORS configuration must:

* Allow the CPM UI origin
* Permit `GET` and `POST` HTTP methods
* Allow required headers such as `Content-Type` and `Authorization`

Once CORS is correctly configured, continue with the node setup and proceed to the next step.
{% endhint %}

**Section 2: Download Required Files**

In this section, you will see the download link(s) for the required DAR files as well as installation instructions to follow on your validator node:

1. Download the CPM DAR file(s)
2. Connect to your Canton console
3. Upload the DAR file(s)
4. Verify installation and test your setup.

Follow the instructions carefully to ensure your node is set up correctly.

![Node Setup](/files/hYMocOJKwtn9xvTEEZFD)
{% endstep %}
{% endstepper %}


---

# 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.catalyx.solutions/catalyx-package-manager/registration-guide.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.
