This app is part of Credimi Extras. Automate all your EUDI testing with Credimi

Pub-EAA Provider Application

List Selection

Target List: eu_credimi_pub-eaa_trust_registry_infrastru — Credimi Pub-EAA Trust Registry Infrastructure (eu_credimi_pub-eaa_trust_registry_infrastru)

Choose the Pub-EAA Providers list of the Member State that notified this provider.

Entity Information

The legal entity applying to be listed as a provider of publicly issued electronic attestations of attributes (Pub-EAA). Enter the exact registered provider name.

ISO 3166-1 alpha-2 code of the Member State that notified this provider. It is published in the entity role URI.
When one exists: the identifier registered in official records that unambiguously identifies the provider. Use organizationIdentifier semantics for a legal entity or serialNumber semantics for a natural person. Published in TETradeName.
The Union or national act under which the attestations are issued. Start with EU for Union law or the EU Member State's two-letter ISO country code for national law, then the unique law identifier. Published in TETradeName as an OJ: URI; the scheme prefix is added for you.
Legal name of the organisation (English).
Optional trading name if different from legal name.
Postal Address
Two-letter country code, e.g. IT for Italy.
Public URL of the policies and terms under which the provider issues attestations. Published as the entity's information URI.
Published as a mailto: URI; the profile requires the entity to be contactable by email.
International form. Published as a tel: URI.

Services

At least one service must be registered.

Service 1

Select the Pub-EAA service type. Register issuance, revocation, or both.
Human-readable service name (English).
Optional. The certificate used to verify signatures or seals created by the Pub-EAA Provider on issued attestations, or the certificate of the CA that issues those attestation-signing certificates. More than one may be supplied, provided they carry the same public key and an identical subject. Upload an X.509 certificate beginning with -----BEGIN CERTIFICATE-----. For testing, you can generate a self-signed certificate using our Certificate creation guide. Never upload the private key.

The certificate is published as the service ServiceDigitalIdentity, so its subject must identify the provider: set the organisation (O) to exactly the Entity Name entered above. It may be self-signed or issued by a CA — this publisher does not build or verify a certification path, so a self-signed certificate is accepted.

Required Documents

The following documents are required for a real application. For this testing tool, document upload is not implemented.

  • {ONBOARDING_AUTHORIZATION}.md
  • {SERVICE_PROVIDER_AGREEMENT}.md

Notification

Being listed states that this provider is currently notified by the Responsible Member State. Every service is published with the status notified and a status starting time taken from the publication event. If the notification is withdrawn, a new immutable list version is published in which every service reads withdrawn and the previous notified state is kept in the service history.

Cancel