Skip to content

Opaque field ignored #5

@samizdatco

Description

@samizdatco

the opaque field is not used when generating challenges, nor is it validated when included in an authentication request. is this a significant omission? the spec makes it seem as though it only exists as a convenience to stash state in, but i could believe some software out there depends upon it...

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions