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

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

                Author: ASF GitHub Bot
            Created on: 12/Aug/26 08:31
            Start Date: 12/Aug/26 08:31
    Worklog Time Spent: 10m 
      Work Description: smolnar82 commented on PR #1342:
URL: https://github.com/apache/knox/pull/1342#issuecomment-5264314729

   > Some RFC 8693 token exchange related constants were moved from 
TokenExchangeHandler
   to JWTFederationFilter so that the tests outside the package, namely
   JWTFederationFilterTokenExchangeTest, can read the values.
   
   I think this is the wrong approach: those constants should be in 
`TokenExchangeHandler` and the test should have been added in the same package 
(now everything is in the `...filter` package, but the test is outside. I'll 
file a follow-up JIRA to resolve this.




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

    Worklog Id:     (was: 1035330)
    Time Spent: 50m  (was: 40m)

> Extend JWTFederationFilter for dynamic JWKS and iss attribute on 
> token-exchange
> -------------------------------------------------------------------------------
>
>                 Key: KNOX-3405
>                 URL: https://issues.apache.org/jira/browse/KNOX-3405
>             Project: Apache Knox
>          Issue Type: Task
>          Components: JWT
>            Reporter: Harrison Sheinblatt
>            Assignee: Harrison Sheinblatt
>            Priority: Major
>          Time Spent: 50m
>  Remaining Estimate: 0h
>
> Extend JWTFederationFilter in two ways: (1) store the validated token's iss 
> claim as a request attribute for downstream handlers; and (2) for 
> grant_type=token-exchange, when the static jwt.expected.issuer check fails, 
> consult TrustedOidcIssuerService — calling resolveJwksUri() for dynamic-JWKS 
> issuers, which in turn uses the OIDC discovery document cache.



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

Reply via email to