[jira] [Work logged] (KNOX-2859) Search/filter tokens on Token Management page

["ASF GitHub Bot (Jira)" <ji...@apache.org>]

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

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

                Author: ASF GitHub Bot
            Created on: 06/Jan/23 15:46
            Start Date: 06/Jan/23 15:46
    Worklog Time Spent: 10m 
      Work Description: smolnar82 opened a new pull request, #713:
URL: https://github.com/apache/knox/pull/713

   ## What changes were proposed in this pull request?
   
   Replaced the old Angular2 Datatable with a more modern Material Table implementation and configured filtering, sorting, and pagination on both tables on the Token Management UI.
   
   ## How was this patch tested?
   
   Manual testing with a huge amount of tokens created (2k) to ensure the new implementation still performs.
   




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

            Worklog Id:     (was: 837511)
    Remaining Estimate: 0h
            Time Spent: 10m

> Search/filter tokens on Token Management page
> ---------------------------------------------
>
>                 Key: KNOX-2859
>                 URL: https://issues.apache.org/jira/browse/KNOX-2859
>             Project: Apache Knox
>          Issue Type: Improvement
>          Components: TokenManagementUI
>    Affects Versions: 2.0.0
>            Reporter: Sandor Molnar
>            Assignee: Sandor Molnar
>            Priority: Major
>             Fix For: 2.1.0
>
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> In 2.0.0, the Knox team introduced a new UI where logged-in users can see their own tokens as well as tokens generated by them on behalf of other users (impersonated tokens).
> These tables show different useful information, such as custom metadata, in tables where pagination is used. However, there is no way that end-users can filter/search for specific tokens based on their needs. In the case of a huge token list (e.g. when the token limit is disabled), it may be very hard for them to find the token they are interested in (e.g. they want to revoke/disable one).
> The scope of this task is to find another Angular DataTable implementation where these features are supported and integrate them on the token management page (we may want to do the same on tables on the Admin UI).



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