[
https://issues.apache.org/jira/browse/KNOX-2624?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17378771#comment-17378771
]
ASF subversion and git services commented on KNOX-2624:
-------------------------------------------------------
Commit a821cf3c5eb61cd71d456f3dc5fa4da6d5a04dbd in knox's branch
refs/heads/master from Sandor Molnar
[ https://gitbox.apache.org/repos/asf?p=knox.git;h=a821cf3 ]
KNOX-2624 - Introducing Knox Token Management UI (#461)
> Introducing token management page
> ---------------------------------
>
> Key: KNOX-2624
> URL: https://issues.apache.org/jira/browse/KNOX-2624
> Project: Apache Knox
> Issue Type: Improvement
> Affects Versions: 1.6.0
> Reporter: Sandor Molnar
> Assignee: Sandor Molnar
> Priority: Critical
> Time Spent: 50m
> Remaining Estimate: 0h
>
> It'd be greate to add management capabilities through a table that contains
> all of the tokens for the authenticated user.
> The Token Management page will contain a table of all active and disabled
> tokens for the authenticated user like this:
> |token-id|comment|created|expiration|status|actions|
> | | | | | | |
> Token actions may include:
> # Disable/Enable based on the current status
> # Revoke
> Actual tokens must not be rendered in the table and are only available for
> copying from the generation page. Since only hashes of the tokens are stored
> this is a hard requirement and a security best practice. If end-users lose
> access to their token, they should revoke it and generate a new one.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
