You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@knox.apache.org by "Sandor Molnar (Jira)" <ji...@apache.org> on 2026/09/09 07:53:00 UTC

[jira] [Resolved] (KNOX-3433) knoxidf token exchange response must include issued_token_type

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

Sandor Molnar resolved KNOX-3433.
---------------------------------
    Fix Version/s: 3.1.0
       Resolution: Fixed

> knoxidf token exchange response must include issued_token_type
> --------------------------------------------------------------
>
>                 Key: KNOX-3433
>                 URL: https://issues.apache.org/jira/browse/KNOX-3433
>             Project: Apache Knox
>          Issue Type: Task
>          Components: JWT
>            Reporter: Harrison Sheinblatt
>            Assignee: Sandor Molnar
>            Priority: Major
>             Fix For: 3.1.0
>
>          Time Spent: 0.5h
>  Remaining Estimate: 0h
>
> RFC 8693 §2.2.1 requires the response include issued_token_type
> It's not set now by knoxidf.
> The correct value to set is "urn:ietf:params:oauth:token-type:jwt". While access_token may be OK in some circumstances, since we're returning a jwt that is meant to be used as a jwt for possible future exchanges and authz, so the client might parse it to get, for example, group claims, jwt is correct here.
> Note that OAuthResource does set the field in the response, but hardcodes it to access_token and has different logic than the base knoxtoken TokenResource, so it's unclear we want to inherit from that and refactor it to allow the jwt value. 



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