[jira] [Updated] (KNOX-3129) Add Expiration to CLIENTID and APIKEY API Responses

["Sandor Molnar (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/KNOX-3129?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Sandor Molnar updated KNOX-3129:
--------------------------------
    Fix Version/s: 3.0.0
                       (was: 2.2.0)

Due to the pending 2.1.0 release this JIRA has been pushed out to 3.0.0 as part of a bulk update. If there is a specific reason to pull this back into the 2.1.0 release and you intend to provide a PR in the next few days please provide justification and reset the Fix Version to 2.1.0.

> Add Expiration to CLIENTID and APIKEY API Responses
> ---------------------------------------------------
>
>                 Key: KNOX-3129
>                 URL: https://issues.apache.org/jira/browse/KNOX-3129
>             Project: Apache Knox
>          Issue Type: Improvement
>          Components: Server
>            Reporter: Larry McCay
>            Assignee: Larry McCay
>            Priority: Major
>             Fix For: 3.0.0
>
>          Time Spent: 20m
>  Remaining Estimate: 0h
>
> While both the CLIENTID and APIKEY APIs default the knox.token.ttl to -1 to never expire, we do not prevent actual expirations. In the case that there is a configured expiration, return the expiration in the response as appropriate for the clients.



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