arf-presentation-reqs

To securely present wallet attributes to a relying party, you must authenticate the relying party instance, verify requested attributes against registered ones, evaluate disclosure policies, and explicitly approve the presentation flow.

Relying party authentication in EUDI wallet attribute presentation verifies the identity of the service provider requesting your data, ensuring the requester is legitimate before you approve sharing any personal attributes from your wallet.

You verify requested attributes by checking if the relying party is authorized to receive only the specific attributes they requested, comparing them against your registered data before evaluating any embedded issuer disclosure policies.

You need to evaluate issuer disclosure policies during attribute presentation when sharing specific attestation data, ensuring any issuer-defined rules on how attributes can be shared with the relying party are enforced before user approval.

Yes, you can deny the presentation of specific attributes through the user approval flow, which guides you through explicitly approving or rejecting the sharing of requested attributes with the relying party before any data leaves your wallet.

Relying party instance authentication focuses solely on verifying the service provider identity and obtaining user consent for attribute presentation; it does not manage the initial issuance or storage of the wallet attributes themselves.