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

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

                Author: ASF GitHub Bot
            Created on: 11/Aug/21 12:10
            Start Date: 11/Aug/21 12:10
    Worklog Time Spent: 10m 
      Work Description: zeroflag commented on pull request #480:
URL: https://github.com/apache/knox/pull/480#issuecomment-896771977


   cc: @pzampino @smolnar82 @moresandeep @lmccay 


-- 
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.

To unsubscribe, e-mail: dev-unsubscr...@knox.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


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

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

> TokenResource Renew and Revoke Should Respond With Error Codes That Identify 
> Specific Errors
> --------------------------------------------------------------------------------------------
>
>                 Key: KNOX-2396
>                 URL: https://issues.apache.org/jira/browse/KNOX-2396
>             Project: Apache Knox
>          Issue Type: Improvement
>          Components: Server
>    Affects Versions: 1.4.0
>            Reporter: Philip Zampino
>            Assignee: Attila Magyar
>            Priority: Major
>          Time Spent: 20m
>  Remaining Estimate: 0h
>
> TokeResource currently responds to failed requests to renew or revoke a token 
> with a boolean indicator and an error message. Any client behavior based on 
> the nature of the failure must currently depend on the error message content, 
> which is not robust.
> These error responses should also include one of a well-defined set of error 
> codes, on which clients can reliably depend to control their behavior upon 
> receiving such responses.



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

Reply via email to