[
https://issues.apache.org/jira/browse/KNOX-3279?focusedWorklogId=1010919&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-1010919
]
ASF GitHub Bot logged work on KNOX-3279:
----------------------------------------
Author: ASF GitHub Bot
Created on: 23/Mar/26 14:19
Start Date: 23/Mar/26 14:19
Worklog Time Spent: 10m
Work Description: pzampino opened a new pull request, #1182:
URL: https://github.com/apache/knox/pull/1182
## What changes were proposed in this pull request?
Added custom dispatches for the REST Catalog API (ICEBERG-REST) which can
convey configurable token metadata as headers in the outbound dispatch request
(e.g., userName --> X-Knox-Meta-userName header).
## How was this patch tested?
Added two new tests for the respective dispatches (RestCatalogDispatchTest,
RestCatalogHaDispatchTest), ran a full `clean verify`, and manually tested with
a local installation.
Issue Time Tracking
-------------------
Worklog Id: (was: 1010919)
Remaining Estimate: 0h
Time Spent: 10m
> 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: 10m
> 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)
