iotaledger / iotaledger/identity

Credential validation process takes public key as parameter instead of attempting to fetch it

Open
#1,779 0 comments 0 reactions 0 assignees View on GitHub
Breaking change Enhancement
Dominant language
Rust
Stars
346
Forks
100
Avg merge
13h 41m
Merged PRs (30d)
2

Description

## Description
When re-design credential (plaintext, JWT, SD-JWT, SD-JWT VC, and so on) validation don't attempt to fetch the verification key by analyzing the credential itself, instead have the user supply it.

## Motivation
It is impossible to take into account every possible way an issuer might reference the verification key in the credential itself.

Contributor guide

Open the contributing guide

Research direction

No files or tests are named; begin by locating the credential validation entry points for plaintext, JWT, SD-JWT, and SD-JWT VC credentials. Define the affected API boundary and verify that validation uses a caller-supplied public key rather than fetching one from the credential, consistently across those formats.

Written by the indexing model from the issue text.

Assessment

Tech stack
rust
Domain
authentication, security
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.