Skip to content

options.maxAge shouldn't use milli seconds #273

Closed
@mborst

Description

@mborst

options.maxAge shouldn't allow milliseconds because it compares against the iat claim from the token, which is in seconds.

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions