dotCMS / dotCMS/core

Token Expiration message too vague to action

Open
#35,141 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

stale Team : UX Triage
Dominant language
Java
Stars
970
Forks
486
Avg merge
3d 33m
Merged PRs (30d)
170

Description

Define the Problem

When I log into the back end of dotCMS I am sometimes greeted with a message that tells me some API tokens are about to expire and to please review them. The message gives me a link to an output that gives me the Expiration Date in a numbers string (so I have no idea what it translates to for an actual date), a 'id' that I have no idea what it relates to (token id?), and a userId with a name that does not match any user in my system.

This message should provide me instead with the date the token will expire and how many days until it expires. It should tell me the name of the user the token is for, and it should tell me the name of the token, so I as an administrator can navigate to the proper user and API token and renew it if needed. The message should enable someone using the back end UI to do the administration.

See screen shots below

Who's Facing the Problem?

dotCMS administrators that manage API tokens for users

Screenshot or Video
Image Image
Relevant Links and Resources

No response

Assumptions & Initiation Needs

No response

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by tracing the backend UI warning about expiring API tokens and the output linked from that message. Identify how the expiration date, user, and token are currently presented, then verify that administrators can identify the affected user and token, understand the expiration date and remaining days, and navigate to renew it.

Written by the indexing model from the issue text.

Assessment

Tech stack
java
Domain
authentication, backend
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
52/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.