Skip to content

did-jwt's JwtPayload type incorrectly specifies sub as an obligatory field #158

@devceline

Description

@devceline

It needs to be marked as optional, as many of our specs do not specify sub as needed even though sub is a usually required field in many specs

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions