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

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

                Author: ASF GitHub Bot
            Created on: 19/May/21 07:53
            Start Date: 19/May/21 07:53
    Worklog Time Spent: 10m 
      Work Description: smolnar82 opened a new pull request #449:
URL: https://github.com/apache/knox/pull/449


   ## What changes were proposed in this pull request?
   
   Added more refined validation on each token lifespan field to make sure we 
do not allow:
   - negative values
   - floating numbers
   - out-of-range values:
     - days: 0- 3650
     - hours: 0 - 23
     - mins: 0- 59
   - empty input
   
   ## How was this patch tested?
   
   Manually tested with different combinations of the lifespan input fields.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
[email protected]


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

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

> Knox Token Generation UI should have Validation checks for invalid lifetimes
> ----------------------------------------------------------------------------
>
>                 Key: KNOX-2605
>                 URL: https://issues.apache.org/jira/browse/KNOX-2605
>             Project: Apache Knox
>          Issue Type: Bug
>    Affects Versions: 1.6.0
>            Reporter: Saksham Puri
>            Assignee: Sandor Molnar
>            Priority: Major
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> *Problem Description:*
> The Token Generation UI should validate invalid lifetimes and throw "Invalid 
> Lifetime" warning message.
> Following are the conditions to have Validation Check for [D,H,M]:
>  * Check with -ve values 
>  * Check with decimal values
>  * Check with empty values
>  * Check Integer MAX value
> PS: Currently, it gives invalid lifetime warning only when D,H,M are all set 
> to 0.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to