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

ASF subversion and git services commented on KNOX-2859:
-------------------------------------------------------

Commit 5a70e628a74de26cf4b2370443777cd58abe64bf in knox's branch 
refs/heads/master from Sandor Molnar
[ https://gitbox.apache.org/repos/asf?p=knox.git;h=5a70e628a ]

KNOX-2859 - Token Management UI improvements (#713)

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.

> 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: 1.5h
>  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)

Reply via email to