Skip to content

Token management: Last accessed timestamp is unclear when token has not been used yet #22036

@mako42

Description

@mako42

Minor nitpick, but when a token has not been used yet, it shows the standard unix start date of 1970-1-1 as "last accessed". I can imagine this can be confusing to a user, so showing "never" might be easier to understand.

Image

Expected Behavior

When a token has not been used yet, it should not show a wrong time stamp under last accessed.

Current Behavior

For unused tokens, a wrong (and potentially confusing) date is shown.

Possible Solution

Steps to Reproduce (for bugs)

  1. TestQuality TC1163

Context

Your Environment

  • Graylog Version: 6.2.0-beta.1-1
  • Java Version:
  • OpenSearch Version: 2.19.1
  • MongoDB Version: 8.0
  • Operating System:
  • Browser version: firefox snap on ubuntu

Metadata

Metadata

Assignees

No one assigned

    Type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions