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

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

                Author: ASF GitHub Bot
            Created on: 03/Sep/26 14:21
            Start Date: 03/Sep/26 14:21
    Worklog Time Spent: 10m 
      Work Description: github-actions[bot] commented on PR #1375:
URL: https://github.com/apache/knox/pull/1375#issuecomment-5527196479

   ## Test Results
     4 files    4 suites   16s ⏱️
    84 tests  84 ✅ 0 💤 0 ❌
   102 runs  102 ✅ 0 💤 0 ❌
   
   Results for commit d5ae0441.
   
   
[test-results]:data:application/gzip;base64,H4sIAGSCmWoC/13MSw6DIBSF4a0Yxh1c9EKxm2koQnJTlYbHyHTvRaOWdvj9JzkLczTayG4NXhoWM6UTQw46kZ8LuSwuS1o3hQfuMRvzV570KgXO4DSNP8GG4MNeQp7XRw7tjuOxLt/HzdXh5vrP+GmiVMAGoS0gcgWdFUZ0DnqU2lx7Yzk+WlDaSiVhYO8PuFJRbwIBAAA=
   




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

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

> 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
>          Time Spent: 20m
>  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)

Reply via email to