Skip to end of metadata
Go to start of metadata
This chapter describes the metadata the participants must supply, how the Beheerorganisatie publishes the aggregated metadata, and how it is to be interpreted by the participants.

Participants must use SAML metadata in the network to describe the URLs and certificates that are used for the different interfaces. Participants supply metadata and the Beheerorganisatie validates, aggregates and publishes it according to Proces netwerkmetadata.

Moreover, service providers adapting to the standard DV-HM interface specifications, MUST exchange SAML metadata with their supporting HM systems based on specifications describes in this chapter.

  • DV metadata for HMFor each service, a Dienstverlener (DV) MUST supply metadata to the HM as a valid SAML file according to urn:oasis:names:tc:SAML:2.0:metadata with one signed EntityDescriptor element.
  • HM metadata for DVA Herkenningsmakelaar (HM) MUST supply metadata to the service provider as a valid SAML file according to urn:oasis:names:tc:SAML:2.0:metadata with one signed EntityDescriptor element.
  • Metadata for participantsA participant MUST supply metadata to the Beheerorganisatie (BO) for every system that implements the role of HM, AD, MR or KR in the network. A participant MUST NOT supply metadata for a role or functionality it has not been assigned.
  • Network metadataThe Beheerorganisatie checks the participants' metadata for conformity, deletes the signatures and aggregates the metadata into one file.

  • No labels