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

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

                Author: ASF GitHub Bot
            Created on: 23/Mar/26 14:41
            Start Date: 23/Mar/26 14:41
    Worklog Time Spent: 10m 
      Work Description: github-actions[bot] commented on PR #1182:
URL: https://github.com/apache/knox/pull/1182#issuecomment-4111149817

   ## Test Results
   7 tests   7 ✅  1s ⏱️
   1 suites  0 💤
   1 files    0 ❌
   
   Results for commit 47e56df7.
   
   
[test-results]:data:application/gzip;base64,H4sIAAlRwWkC/1WMSQ7CMBAEvxL5zAHjZWQ+g0ZepBFJjLycEH/HCUlwbl3VUr1ZoNFndh/4ZWC5UjnA1YSF4rxhO8pywb4fuVp7Fk96NXE9REAaT8KnFNNmUp333jL73I//tZW72Mp9y8ZpotKASfBKuwAShXZCcrRGaW1QWbiB4cIpYRSIwD5fJHPc1/sAAAA=
   




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

    Worklog Id:     (was: 1010927)
    Time Spent: 0.5h  (was: 20m)

> REST Catalog dispatch implementation for including configurable metadata as 
> outbound request headers
> ----------------------------------------------------------------------------------------------------
>
>                 Key: KNOX-3279
>                 URL: https://issues.apache.org/jira/browse/KNOX-3279
>             Project: Apache Knox
>          Issue Type: Improvement
>          Components: Server
>            Reporter: Philip Zampino
>            Assignee: Philip Zampino
>            Priority: Major
>          Time Spent: 0.5h
>  Remaining Estimate: 0h
>
> For Iceberg REST Catalog proxying, Knox should support the ability to convey 
> a configurable set of token metadata elements associated with the client 
> credentials from the inbound request as headers in the outbound (dispatch) 
> request.
> A custom dispatch for the ICEBERG-REST service should be implemented to 
> provide this support.
> Proposed topology contents (example):
> {code:java}
>     <service>
>         <role>ICEBERG-REST</role>
>         <param>
>             <name>token-metadata-headers</name>
>             <value>email,category</value>
>         </param>
>     </service> {code}
> If the configured metadata items don't exist for a given client_id, then no 
> headers for those items should be conveyed in the outbound request (i.e., 
> they should be ignored).
>  
> It's not clear whether the standard {{userName}} metadata item should be 
> included by default.
> The resulting header names can be of the form {{X-Knox-Meta-<ITEM_NAME>}} 
> where {{<ITEM_NAME>}} is the token metadata item name.



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

Reply via email to