Catalogs
Catalog id: resource.catalogs.catalogs
Status: stub
Open it
| Navigation | resources / catalogs / catalogs |
| Deep link | #tenant={tenant}&resource=catalogs&rarea=catalogs |
| Scope | tenant |
Catalog list and catalog page
The screen opens on the list of every catalog of the tenant, with its slug and status. Selecting a row opens that catalog on its own page, titled with the catalog name; All catalogs returns to the list. Every action on the catalog page (make available on the web, link a type, import a remote catalog, import from an issuer) acts on that catalog only, and each dialog names the catalog it targets.
Adding a credential type
Link a type offers three sources:
| Source | Type identifier | Format |
|---|---|---|
| Credential configuration | VCT or doctype of the configuration (or of its bound design) | Taken from the configuration, read only |
| Credential design | Resolved by the catalog from the design | Taken from the design, read only |
| From scratch | Entered: a URI, or a doctype for mso_mdoc | Chosen by the operator |
The request is POST /api/catalog/v1/catalogs/{catalogId}/schemas/link with vct or doctype,
explicit schemaURIs, and designId for a design. vctId is reserved for hosted VCT registry ids
and is not sent for a VCT value.
Import from an issuer
Import from issuer links every credential configuration of the chosen issuer into a new catalog or an existing one (on a catalog page: that catalog). Configurations typed by their bound credential design are included. The result lists how many were imported, which failed and why, and which were skipped because they carry no type the catalog can list.
Public page
A published catalog is served on the tenant host at /catalog-console/catalogs/{slug}, backed by the
public TS 11 API at /public/catalogs/{slug}/api/v1. The page has a branded header (tenant logo and
catalog name, navigation, light and dark switch), the credential gallery, and a footer that points
developers at the API.