Test environment · wmp.dev.triveria.io

WMP service discovery

Participant discovery for WMP as CS-15 §7.3 describes it: a BDXL DNS zone that points every registered participant at an OASIS SMP 1.0 server, which returns its signed endpoints. QTSPs register participants through one API call.

Endpoints

SMP

https://smp.wmp.dev.triveria.io

OASIS SMP 1.0, read-only. Answers GET on the service group and the signed service metadata of a participant. Nothing else is exposed.

BDXL DNS

ns.wmp.dev.triveria.io

Authoritative for wmp.dev.triveria.io, delegated from the parent zone, so any resolver finds it. Participant records live under bdxl.wmp.dev.triveria.io.

SMP signing certificate

smp-signing.crt

Pin it: every service metadata response is signed with this key. SHA-256 fingerprint:

openssl x509 -in smp-signing.crt -noout -fingerprint -sha256

How it works

  1. Register. A QTSP sends the participant's Subscriber certificate and services to the registration API. It writes the participant's entry to the SMP, which signs it, and adds the participant's U-NAPTR records to the DNS zone. Both are live within a second or two.
  2. Discover. A client hashes the participant id, queries the NAPTR record under bdxl.wmp.dev.triveria.io and gets the SMP's URL back.
  3. Fetch and verify. It fetches the participant's service metadata from the SMP and checks the signature against the pinned SMP certificate.
  4. Connect. The metadata lists the participant's endpoints, each carrying its Subscriber certificate. The client opens the WMP session there.

Look up a participant

The same steps a client takes, with standard tools. Enter an id to fill in the commands.

ISO 6523 <ICD>:<id>, or the WMP form ebcore:iso6523:<ICD>:<id>.

1. The DNS names

The BDXL hash is the lowercase base32 of SHA-256 over the lowercased id, without padding. WMP-EDELIVERY §3.1 is ambiguous about what gets hashed, so every participant is published under three names. Any of them works.

VariantName
stdlzmedsmzxyd37yc74tzvpycmuanfcmn667jhgbfqddrvmse6nyta.iso6523-actorid-upis.bdxl.wmp.dev.triveria.io
wmplzmedsmzxyd37yc74tzvpycmuanfcmn667jhgbfqddrvmse6nyta.iso6523.bdxl.wmp.dev.triveria.io
wmp-efauwjmhd6bkke5qbqizqccg5thy3i3awfzo7wcyk4so44wd4xyka.iso6523.bdxl.wmp.dev.triveria.io

The std hash in a shell:

printf '%s' '0088:4035811991021' | tr A-Z a-z | openssl dgst -sha256 -binary | base32 -w0 | tr -d = | tr A-Z a-z

2. Find the SMP

dig +short NAPTR lzmedsmzxyd37yc74tzvpycmuanfcmn667jhgbfqddrvmse6nyta.iso6523-actorid-upis.bdxl.wmp.dev.triveria.io

A registered participant answers with the SMP's URL; an unknown one with nothing (NXDOMAIN):

100 10 "U" "Meta:SMP" "!^.*$!https://smp.wmp.dev.triveria.io!" .

3. Fetch the service metadata

curl 'https://smp.wmp.dev.triveria.io/iso6523-actorid-upis::0088:4035811991021/services/busdox-docid-qns::urn:wmp:session:v0.1'

A SignedServiceMetadata document: the ServiceMetadata plus an enveloped XML signature (RSA-SHA256) by the SMP key. The service group lists what the participant publishes:

curl 'https://smp.wmp.dev.triveria.io/iso6523-actorid-upis::0088:4035811991021'

4. Verify the signature

Check it against smp-signing.crt, not against a certificate inside the response. If you use Python with lxml (or signxml): lxml adds a stray xmlns="" when it canonicalises a sub-element, and valid signatures fail. The testbed's resolve.py shows the workaround.

Register participants

Through https://registry.wmp.dev.triveria.io. One call publishes both the SMP entry and the DNS records. You need:

Register or replace

export REGISTRY=https://registry.wmp.dev.triveria.io
export REGISTRY_AUTH='<user>:<password>'

jq -n --rawfile cert subscriber.crt \
  '{certificate: $cert, services: [{process: "wmp-evidence", host: "qerds.qtsp.example"}]}' |
curl -u "$REGISTRY_AUTH" -X PUT -H 'Content-Type: application/json' --data @- \
  "$REGISTRY/participants/0088:4035811991021"

The request body:

{
  "certificate": "-----BEGIN CERTIFICATE-----\nMIIB…\n-----END CERTIFICATE-----\n",
  "services": [
    { "process": "wmp-evidence", "host": "qerds.qtsp.example" },
    { "process": "wmp-general",  "host": "wmp.qtsp.example" }
  ]
}

201 Created for a new participant, 200 OK when it replaced one. The response is the participant as published:

{
  "id": "0088:4035811991021",
  "wmp_id": "ebcore:iso6523:0088:4035811991021",
  "certificate": "-----BEGIN CERTIFICATE-----\n…",
  "services": [{ "process": "wmp-evidence", "host": "qerds.qtsp.example" }],
  "dns": {
    "std": "lzmedsmzxyd37yc74tzvpycmuanfcmn667jhgbfqddrvmse6nyta.iso6523-actorid-upis.bdxl.wmp.dev.triveria.io",
    "wmp": "lzmedsmzxyd37yc74tzvpycmuanfcmn667jhgbfqddrvmse6nyta.iso6523.bdxl.wmp.dev.triveria.io",
    "wmp-e": "fauwjmhd6bkke5qbqizqccg5thy3i3awfzo7wcyk4so44wd4xyka.iso6523.bdxl.wmp.dev.triveria.io"
  },
  "warnings": []
}

Read and remove

curl -u "$REGISTRY_AUTH" "$REGISTRY/participants"                     # every registered id
curl -u "$REGISTRY_AUTH" "$REGISTRY/participants/0088:4035811991021"  # one participant
curl -u "$REGISTRY_AUTH" -X DELETE "$REGISTRY/participants/0088:4035811991021"  # 204
CallScopeResult
GET /participantsparticipants:read{"participants": ["<id>", …]}
GET /participants/{id}participants:readThe participant, or 404
PUT /participants/{id}participants:write201 registered, 200 replaced
DELETE /participants/{id}participants:write204, or 404 if not registered

Rules

Errors

StatusMeaning
401Missing or wrong credentials
403The credentials lack the scope for this call
404The participant is not registered
422Invalid input: a bad id, certificate, process or host. detail says which
502The SMP refused the change or is unavailable. Retry

What gets published

For participant ebcore:iso6523:<ICD>:<id> with a service wmp-evidence at qerds.qtsp.example:

WhereWhat
DNSThree U-NAPTR records (std, wmp, wmp-e), service Meta:SMP, pointing to https://smp.wmp.dev.triveria.io. TTL 60 s
SMP service groupiso6523-actorid-upis::<ICD>:<id>
Documentbusdox-docid-qns::urn:wmp:session:v0.1
Processwmp-process::wmp-evidence, one per service
Endpoints bdxr-transport-wmp-ws-v0p1 → wss://qerds.qtsp.example/wmp
bdxr-transport-wmp-https-v0p1 → https://qerds.qtsp.example/wmp
Each carries the participant's Subscriber certificate.
SignatureOver the whole ServiceMetadata, by the SMP signing key

A participant counts as QERDS-capable (CS-15 §7.3) when it has a wmp-evidence process with one of these transport profiles.

Good to know