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.
Test environment · wmp.dev.triveria.io
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.
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.
https://registry.wmp.dev.triveria.io
Registers, replaces and removes participants. HTTP Basic auth. OpenAPI: /docs, /openapi.json.
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.
Pin it: every service metadata response is signed with this key. SHA-256 fingerprint:
openssl x509 -in smp-signing.crt -noout -fingerprint -sha256
bdxl.wmp.dev.triveria.io and gets the SMP's URL back.The same steps a client takes, with standard tools. Enter an id to fill in the commands.
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.
| Variant | Name |
|---|---|
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 |
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
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!" .
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'
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.
Through https://registry.wmp.dev.triveria.io. One call publishes both the SMP entry and the DNS records.
You need:
ebcore:iso6523:<ICD>:<id>.wmp-evidence and the host
that serves /wmp.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": []
}
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
| Call | Scope | Result |
|---|---|---|
| GET /participants | participants:read | {"participants": ["<id>", …]} |
| GET /participants/{id} | participants:read | The participant, or 404 |
| PUT /participants/{id} | participants:write | 201 registered, 200 replaced |
| DELETE /participants/{id} | participants:write | 204, or 404 if not registered |
<ICD>:<id> or ebcore:iso6523:<ICD>:<id>.PUT replaces the participant's certificate and its whole service list. To add a
service, send the existing ones too. Each process may appear once.warnings, so non-conformant certificates can still be tested. One that isn't PEM is rejected.host is a host name with an optional port, no scheme or path.PUT is safe to retry.| Status | Meaning |
|---|---|
401 | Missing or wrong credentials |
403 | The credentials lack the scope for this call |
404 | The participant is not registered |
422 | Invalid input: a bad id, certificate, process or host. detail says which |
502 | The SMP refused the change or is unavailable. Retry |
For participant ebcore:iso6523:<ICD>:<id> with a service
wmp-evidence at qerds.qtsp.example:
| Where | What |
|---|---|
| DNS | Three U-NAPTR records (std, wmp, wmp-e), service
Meta:SMP, pointing to https://smp.wmp.dev.triveria.io. TTL 60 s |
| SMP service group | iso6523-actorid-upis::<ICD>:<id> |
| Document | busdox-docid-qns::urn:wmp:session:v0.1 |
| Process | wmp-process::wmp-evidence, one per service |
| Endpoints |
bdxr-transport-wmp-ws-v0p1 → wss://qerds.qtsp.example/wmpbdxr-transport-wmp-https-v0p1 → https://qerds.qtsp.example/wmpEach carries the participant's Subscriber certificate. |
| Signature | Over 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.
308); send credentials over HTTPS only.