Search Results

Expired Credential Each credential has a defined validity period. Once this period ends, the credential becomes expired and can no longer be used. Expired credentials are marked with a red ellipse labeled “EXPIRED.” To get a new credential, contact the LEA...

Introduction LEAR Credential Employees are Verifiable Credentials that enable access to various systems and features within the DOME environment.Each credential grants specific permissions, referred to as its “power.” For example: To log in to the DOME ...

Verifiable Credentials are used in the DOME ecosystem as a trusted mechanism for identity, authentication, and authorization.They ensure that both individuals and services can interact securely across the different DOME components — such as the Issuer, the Mar...

LEAR Credentials (LEAR Credential Employee and LEAR Credential Machine) credentials grant specific permissions known as “powers.”Each power combines a function (the logical area of capability) with one or more actions (the specific operations permitted within ...

Introduction After a Verifiable Credential is issued, you will receive an email with a Credential Offer.This offer must be processed using the DOME Digital Wallet, which will activate and securely store your credential so it can be used within the DOME enviro...

After a credential is issued, the receipee of the credential receives an email with a Credential Offer, which allows them to activate the credential with the DOME Digital Wallet. See this guide for the step-by-step information. 

Currently, 3 different types of Verifiable Credentials are used in the DOME ecosystem: LEARCredentialEmployee, LEARCredentialMachine and Gx:LabelCredential. LEAR Credentials are used to identify either an individual or a machine/service. Each LEAR Credential ...

The LEAR Credential Issuer is a web application consisting of a server part, HTML interface, the APIs implementing the OpenIDVCI protocol, and the APIs required by the LEAR Credential Signer program. The LEAR Credential Issuer does not require integration w...

This is a simple program that is installed in the PC of the legal representative. It is intended for self-installation without requiring technical knowledge, though it is expected to be installed by the IT personnel taking care of the personal computer infrast...

The LEAR Credential Issuer is a web application consisting of a server part, HTML interface, the APIs implementing the OpenIDVCI protocol, and the APIs required by the LEAR Credential Signer program. The LEAR Credential Issuer does not require integration w...

This is a simple program that is installed in the PC of the legal representative. It is intended for self-installation without requiring technical knowledge, though it is expected to be installed by the IT personnel taking care of the personal computer infrast...

Description The LEAR Credential Issuer is the main application that manages the credential flow. We assume here that it is specialised in creating LEAR Credentials, though it could be used for other types of credentials. In this context, we will use the term ...

Description This is a simple program provided by DOME that should be installed locally in the PC of the legal representative and that performs the actual signing of the LEAR Credential (there are versions for Windows, Mac and Linux). Alternatively, any organi...

Purpose and scope This runbook explains how a backend service or component can integrate with the Verifier as an Authorization Server (AS) in M2M mode. It provides the end-to-end steps needed by developers: from preparing configuration and credentials, to cal...

Prerequisites Legal entity has completed onboarding in the ecosystem. LEAR can access the Issuer service and issue a LEARCredentialMachine to its machine(s). DID method supported: did:key. Access to developer documentation and test environm...

Purpose and scope This runbook explains how a public client, such as a web or mobile application, can integrate with the Verifier acting as an Authorization Server (AS) using the Authorization Code Flow with PKCE. It provides developers with the end-to-end ...

Prerequisites The legal entity has completed onboarding in the DOME ecosystem. The LEAR has obtained a valid LEAR Credential through the Issuer service. The end user (employee, contractor, etc.) has received a Verifiable Credential issued by the...

Purpose and scope This runbook explains how a confidential client, such as a backend component or secure web application, can integrate with the Verifier acting as an Authorization Server (AS) using the Authorization Code Flow with client_secret_jwt client au...

Prerequisites The legal entity has completed onboarding in the DOME ecosystem. The LEAR has obtained a valid LEARCredentialMachine through the Issuer service. DID method supported: did:key. The confidential client (backend service or secure...

At the top of the Trust Framework we have the EU Trusted Lists. Member States have the obligation to establish, maintain and publish trusted lists with each qualified trust service provider under their control and the services provided by them. In order to al...