[ 
https://issues.apache.org/jira/browse/KNOX-3018?focusedWorklogId=909395&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-909395
 ]

ASF GitHub Bot logged work on KNOX-3018:
----------------------------------------

                Author: ASF GitHub Bot
            Created on: 12/Mar/24 11:20
            Start Date: 12/Mar/24 11:20
    Worklog Time Spent: 10m 
      Work Description: smolnar82 merged PR #878:
URL: https://github.com/apache/knox/pull/878




Issue Time Tracking
-------------------

    Worklog Id:     (was: 909395)
    Time Spent: 20m  (was: 10m)

> Unlimited token generation - Wrong expiration time is shown
> -----------------------------------------------------------
>
>                 Key: KNOX-3018
>                 URL: https://issues.apache.org/jira/browse/KNOX-3018
>             Project: Apache Knox
>          Issue Type: Bug
>          Components: TokenGenerationUI
>    Affects Versions: 2.0.0
>            Reporter: Sandor Molnar
>            Assignee: Sandor Molnar
>            Priority: Major
>             Fix For: 2.1.0
>
>         Attachments: Screenshot 2024-03-11 at 14.25.04.png, Screenshot 
> 2024-03-11 at 14.25.27.png
>
>          Time Spent: 20m
>  Remaining Estimate: 0h
>
> *Steps to reproduce*
>  * set the {{knox.token.ttl}} to {{-1}} in the {{homepage}} topology for the 
> {{KNOXTOKEN}} service
>  * set {{knox.token.lifespan.input.enabled = false}} in the {{homepage}} 
> topology for the {{KNOXTOKEN}} service
> *Actual results*
> With KNOX-3017 in place, the token is generated, but the expiration is wrong, 
> see attached screenshots.
> In addition to this UI bug, the background reaper thread removes this token 
> the next time it's triggered. This is also incorrect: unlimited tokens should 
> never be removed automatically as they never expire.
> *Expected result*
> Token expiration should indicate an unlimited lifespan and unlimited tokens 
> should not be revoked automatically.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to