Introduction
The Identify’s Service Catalog is an implementation of eHerkenning’s Service Catalog requirement and is published at https://[tenant]/runtime/saml2public/servicecatalog. Only SAML2.0 protocol connections whose profiles are eHerkenning appear in the Service Catalog.
The Identify service catalog has the following format:
- IssueInstant: this is the created time at which the service catalog was created (UTC datetime)
- Version: this setting is the version of the service catalog in the format urn:etoegang: <scheme version >:<sequence number>, e.g urn:etoegang:4.3.0.2699:1
- Signature: the service catalog is signed by the Identify signing certificate.
- Per service provider:
- IsPublic: indicates whether the service provider is in public.
- ServiceProviderID: this is the OIN number. You can configure this value in the System Setup page
- OrganizationDisplayName: Organization name. You can configure this value in the System Setup page.
- Per service:
- IsPublic: indicates whether the protocol connection is enabled or not.
- ServiceID (an identifier of a service that is unique in the context of the service provider), ServiceUUID (a universally unique identifier that is used for registering entitlements, SSOSupport (a boolean that indicates if the service supports SingleSignOn) are the settings of the SAML 2.0 protocol connection:
- ServiceName: Identify uses the SAML 2.0 protocol connection name for this attribute.
- ServiceDescription: Identify uses the SAML 2.0 protocol connection description for this attribute.
- ServiceDescriptionURL: Identify uses the SAML 2.0 protocol connection entityID and extra EntityID for this attribute.
- AuthnContextClassRef: Identify uses the SAML 2.0 protocol connection authentication context class for this attribute.
- HerkenningsmakelaarId: it’s the OIN of the Herkenningsmakelaar (HM) that provides the service catalog entry for this service. You can cofigure it in the System Setup page
- EntityConcernedTypesAllowed: Identify uses the list of the Artifact resolution services’ locations for this attribute. In fact, these endpoints are imported from the metadata of a service.
- RequestedAttribute: Identify uses the multi-valued entries of the Attribute consuming services for this attribute.
- ServiceCertificate: Only the valid encryption certificates are included in the Service Catalog.
- Finally, the service catalog is sorted by HerkenningsmakelaarId and then by the ServiceID.