[ 
https://issues.apache.org/jira/browse/KNOX-3068?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Larry McCay updated KNOX-3068:
------------------------------
    Description: 
Need service definition and rewrite rules for Iceberg REST Catalog service. 
This API is a standard from the Iceberg community which provides a REST API 
access to the metastore, associated metadata and cloud storage.

This service definition should be portable to any implementation of the API 
with appropriate trusted proxy support as required for Knox based proxying.

See 
https://github.com/apache/iceberg/blob/main/open-api/rest-catalog-open-api.yaml 
for the open api description.
In conjunction with:

https://issues.apache.org/jira/browse/KNOX-3016
https://issues.apache.org/jira/browse/KNOX-3028

We can support the CLIENT_ID and CLIENT_SECRET issuance, the exchange of those 
for a JWT token to be used as a bearer token and with this patch the dispatch 
to a knox trusing REST Catalog implementation.

  was:Need service definition and rewrite rules for Iceberg REST Catalog 
service.


> Iceberg REST Catalog service definition
> ---------------------------------------
>
>                 Key: KNOX-3068
>                 URL: https://issues.apache.org/jira/browse/KNOX-3068
>             Project: Apache Knox
>          Issue Type: Improvement
>          Components: Server
>    Affects Versions: 2.1.0
>            Reporter: Philip Zampino
>            Priority: Major
>          Time Spent: 0.5h
>  Remaining Estimate: 0h
>
> Need service definition and rewrite rules for Iceberg REST Catalog service. 
> This API is a standard from the Iceberg community which provides a REST API 
> access to the metastore, associated metadata and cloud storage.
> This service definition should be portable to any implementation of the API 
> with appropriate trusted proxy support as required for Knox based proxying.
> See 
> https://github.com/apache/iceberg/blob/main/open-api/rest-catalog-open-api.yaml
>  for the open api description.
> In conjunction with:
> https://issues.apache.org/jira/browse/KNOX-3016
> https://issues.apache.org/jira/browse/KNOX-3028
> We can support the CLIENT_ID and CLIENT_SECRET issuance, the exchange of 
> those for a JWT token to be used as a bearer token and with this patch the 
> dispatch to a knox trusing REST Catalog implementation.



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

Reply via email to