Join with your own participant

In steps 1 to 3 you used Alice, Bob and Charlie, which someone else runs. In this step you become a fourth company. You deploy your own participant on a Kubernetes cluster, get a membership credential from the Authority, and exchange data with Alice.

This step is optional and takes about an hour. It assumes you are comfortable with Kubernetes.

You deploy	Its job, as seen in steps 1 to 3
Wallet	Holds your membership credential (1. Identity)
Control Plane	Publishes your catalog, requests others' catalogs, negotiates contracts (2. Discovery, 3. Data exchange)
HTTP Data Plane	Carries the data for agreed transfers (3. Data exchange)
Dataspace Starter	The same app you used as Alice, now for your own company

The Getting Started guide covers the deployment itself: prerequisites, the CLI, secrets and verification. This page gives you the playground-specific values and what to do once you are running.

Step 1: Get a pre-authorized code

1. Open the Authority Wallet.
2. Click Request Credential, choose PlaygroundCredential and enter your email address.
3. Click Send Email.
4. Open the email from noreply@dataspac.es and copy the pre-authorized code.

Check your spam folder if the email doesn't arrive within a few minutes.

Step 2: Deploy with the playground values

Follow Getting Started from step 2, and fill in the dataspace block of your participant.yaml with these values:

spec:
  dataspace:
    name: playground
    authority:
      did: did:web:playground.dataspac.es:tenants:authority
      domain: playground.dataspac.es
      credentialType: PlaygroundCredential

Keep controlPlane, http-data-plane and dataspace-starter enabled. Use the code from step 1 for the preAuthorizedCodeSecret.

Your host must resolve to your ingress and serve valid TLS. Alice, Bob and Charlie resolve your DID (did:web:<host>:tenants:<id>) over the internet, so a cluster that is only reachable from your own network won't work.

When tsg deploy finishes, sign in to your Wallet at https://<host>/wallet/. A PlaygroundCredential should be listed under your credentials.

Step 3: Repeat the route as yourself

Open your Dataspace Starter at https://<host>/dataspace-starter/, sign in with your administrator account, and redo steps 2 and 3 from your own company:

1. Federated Search: search for httpbin. Alice's, Bob's and Charlie's datasets appear. If the list is empty, click Refresh registry and wait a minute.
2. Tester: pick Alice's participant DID (it ends in tenants:alice), select Alice HTTPBin, choose the GET /anything operation and click Use operation in Tester, then Execute.
3. Try Bob Research HTTPBin. Your participant holds only the membership credential, so the negotiation is refused, just like it was for Alice.

The Tester negotiated and started the transfer for you. To see each part separately, open your Control Plane at https://<host>/control-plane/ and look under Negotiations and Transfers.

Step 4: Offer your own dataset

1. In your Dataspace Starter, open Datasets and click New dataset.
2. Select your HTTP data plane, enter a title, and use https://httpbin.org as the backend URL and https://httpbin.org/spec.json as the OpenAPI specification.
3. Publish, and check the entry under Own Catalog.

Your dataset is now in the playground. Open Alice's Dataspace Starter, go to Browse Participant, and pick your DID to see it from the other side.

See Publishing datasets for versions, metadata and your own backends.

Troubleshooting

Problem	Fix
No credential in your Wallet	Check that the Secret holds the full code and that dataspace.authority matches the values above exactly. Codes expire, so request a new one if needed. Wallet logs: kubectl logs -n <namespace> deploy/<wallet deployment>.
Alice, Bob and Charlie don't show up	The registry synchronizes on an interval. Wait a few minutes and click Refresh registry. Without a credential you won't be listed either.
Negotiation fails for Alice HTTPBin	Check that https://<host>/tenants/<id>/did.json is reachable from the internet. Then check the Control Plane logs.
Anything during deployment	See the troubleshooting section of Getting Started.

Cleaning up

tsg uninstall participant.yaml --delete-data

Your credential stays registered with the Authority. Contact the playground administrators if you need it revoked.