23 docs tagged with "Relying Party"

When designing solutions for the EUDI Wallet Ecosystem, both Relying Parties (RPs) and European Accessibility Act. Providers must consider accessibility requirements that ensure their services are usable by all citizens, including those with disabilities. This document outlines the high-level accessibility frameworks and key considerations for designing accessible solutions.

OpenID4VP gives Relying Parties several mechanisms for checking different types of binding. Which of them work for a given credential depends on the features the issuer provided at issuance time and the relying parties use case:

This page aggregates relevant changes in the German EUDI ecosystem for Relying Parties and EAA Issuers. Where possible, upcoming changes are listed in advance so that integrators can prepare.

Claim binding lets a Relying Party check that the presenter still controls a specific piece of identifying data you bound to the credential at issuance, by comparing a claim you copied into the credential against a fresh presentation of the credential you originally drew it from. A vehicle registration credential can carry the vehicle identification number copied from the vehicle's own registration document; a professional credential can carry the holder's name copied from the identity document used to identify them. Checking the copied claim against a fresh presentation of the original tells the Relying Party that the presenter genuinely still controls the identity or object the claim represents, not merely that they hold a copy of your credential.

Three request parameters recur throughout the binding guarantees: client_id, nonce, and state. The table

Organization Overview

Erica is a public, lightweight, locally-runnable tool designed to help Relying Parties (RPs) accelerate their verifier development and testing. Rather than waiting for integration with the full EUDI Wallet ecosystem, you can use Erica to simulate wallet behavior and test your presentation request handling in isolation.

This page provides a practical reference for Relying Parties integrating with the German Personal Identification Data (PID) credential. It summarizes the key technical details from the German PID Rulebook (PID-DE) that you need to understand in order to successfully request, receive, and verify a PID.

Whether you plan to verify credentials (Relying Party), issue credentials (EAA Provider), or do both, you complete the same onboarding process once. During the Plan stage, simply declare all the roles you intend to fulfill in your use case description.

Key binding - also known as device binding - lets a Relying Party check that the entity presenting your credential is the same entity you issued it to, by requiring that entity to prove control of a device-bound key you bound to the credential at issuance. Without it, a Relying Party can only confirm that a credential is authentic: signed data can be copied exactly, out of a backup, off a compromised device, or out of a badly secured log, without invalidating your signature.

Effective logging and monitoring are critical for transparency, security, and compliance within the EUDI Wallet Ecosystem. The following guidance distinguishes between sandbox and production environments.

Welcome to Germany's EUDI Wallet Sandbox. After your kick-off call, complete the following steps to get access to all resources.

This document provides a non-exhaustive list of open-source libraries that support OpenID4VP (OpenID for Verifiable Presentations). The list is intended as a starting point for Relying Parties exploring OpenID4VP implementations.

Audience: Relying Parties implementing an OpenID4VP flow to enable the consumption of a PID credential in the German EUDI Wallet Ecosystem.

Introduction

This guide provides Relying Party-specific requirements and technical integration steps for organizations that want to verify credentials in the German EUDI Wallet Ecosystem.

Introduction

Session binding ties a presentation to this specific OpenID4VP exchange: the one your backend is waiting on

1. Geltungsbereich

Illustrative scenarios for participants in the EUDI Wallet ecosystem.

Diese Use Policy ergänzt die SPRIND EUDI Wallet Sandbox Nutzungsbedingungen und gilt für alle Teilnehmer in den im Zusammenhang mit der Sandbox stehenden Kommunikationskanälen. Das Ziel ist die Förderung einer professionellen, konstruktiven und respektvollen Testumgebung.

Audience: Relying Parties building OpenID4VP / HAIP presentation requests for the German EUDI Wallet Ecosystem.

Developers testing with the National EUDI Wallet in the Sandbox should be aware of the following details, peculiarities and known bugs.