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

ASF subversion and git services commented on KNOX-3279:
-------------------------------------------------------

Commit be2b9a41e4a7d89e96870da9cd8928df2d8aa04a in knox's branch 
refs/heads/master from Philip Zampino
[ https://gitbox.apache.org/repos/asf?p=knox.git;h=be2b9a41e ]

KNOX-3279 - REST Catalog dispatch implementation for including configurable 
metadata as outbound request headers (#1182)

> 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: 2h 40m
>  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