Project

General

Profile

Actions

action #118894

open

API Key expiration date has a weird lower bound

Added by ph03nix about 2 years ago. Updated about 2 years ago.

Status:
New
Priority:
Normal
Assignee:
-
Category:
Regressions/Crashes
Target version:
QA (public, currently private due to #173521) - future
Start date:
2022-10-14
Due date:
% Done:

0%

Estimated time:

Description

Observation

When creating a new API key, the time can't be set to 00:00:00. The lowest possible value seems to be 0 hours 0 minutes and the seconds system time when the page has been loaded. Thee the following screenshot as illustration:

Here the lowest value was 00:00:39. After reloading the lowest time value changes and I see a correlation between the seconds of my system time and the lowest acceptable time in the input field.

Steps to reproduce

  • Create new API key
  • Try to set the time value to 00:00:00
  • Try again, the lowest acceptable value depends on the page loading time

Impact

Marginal. Increasing the expiration token by several seconds resolves the issue.

Problem

H1: The lowest possible bound is set wrong

Suggestion

  • Well ... Fix the lower bound issue :-)

Workaround

  • Increase the expiration token by some seconds

Files

low.png (25 KB) low.png ph03nix, 2022-10-14 08:43
Actions #1

Updated by okurz about 2 years ago

  • Category set to Regressions/Crashes
  • Target version set to future

Funny bug :)

Actions

Also available in: Atom PDF