Philip Zampino created KNOX-3279:
------------------------------------

             Summary: 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


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