Skip to content

Credentials origin validation #30

@patatoid

Description

@patatoid

As stated in openwallet-foundation/sd-jwt-js#307, credentials signature may be verified against the issuer. Here are given ways to verify the origin server that issued a credential.

One more way is to verify it against a trusted list, both the ETSI (https://www.etsi.org/deliver/etsi_ts/119600_119699/119602/01.01.01_60/ts_119602v010101p.pdf) and the w3c has worked on standards for the creating trust frameworks.

Either way, it would be great to find a way to verify from whom come the credential from to attest an origin. The verifier would then be able to allow / disallow certain origins. The open ecosystem use case being a further step in my opinion.

EDIT

As open ecosystem, I think about ecosystems that do not require a trust framework since credentials are to be trusted to be valid. That trust help for the holders to hold and present credentials safely using computational and secure measures for both the wallets and the verifiers. This makes the ecosystem closed but open for the holders. Trust frameworks navigation is still an ongoing research, trust lists registration may be a simple first implementation.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    Status
    No status

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions