arrow icon indicating copy to clipboard operation
arrow copied to clipboard

Arrow Flight SQL server AuthN and AuthZ

Open Susmit07 opened this issue 1 year ago • 5 comments

Describe the usage question you have. Please include as many useful details as possible.

Hi Team,

If things goes well, we will be using Arrow Flight SQL Server.

We will be publishing sdks for java and python for teams to consume in our organisation.

Flight SQL server is written in Python and we are using DuckDB query engine for query support on S3 parquet files.

sql_query = "SELECT * FROM read_parquet('s3a://bucket/parquets/flights-1m-new-*.parquet');"

The performance numbers are really good.

I want to know how to authenticate and authorize a user (best practices) accessing a parquet data for a bucket. Every teams will have dedicated S3 buckets.

Everytime initialising s3 client with new access and secret keys won't it be resource intensive?

Component(s)

FlightRPC

Susmit07 avatar Oct 17 '24 06:10 Susmit07

Isn't this question more about DuckDB? Flight isn't involved in the S3 access here.

lidavidm avatar Oct 17 '24 06:10 lidavidm

If you just want authentication/authorization, you can implement a middleware to check a bearer token or similar.

lidavidm avatar Oct 17 '24 06:10 lidavidm

Yeah authN i am thinking to use a JWT based authN, you are correct on accessing the s3 buckets by duck db can we initialise s3 client with new access and secret keys every-time do you see any issues here?

Susmit07 avatar Oct 17 '24 06:10 Susmit07

I can't answer for DuckDB - you should ask the DuckDB community.

I don't believe we have an example of JWT specifically but you can implement that yourself with middleware as mentioned.

lidavidm avatar Oct 17 '24 06:10 lidavidm

sure will do.. thank @lidavidm

Susmit07 avatar Oct 17 '24 06:10 Susmit07

This issue has been marked as stale because it has had no activity in the past 365 days. Please remove the stale label or comment below, or this issue will be closed in 14 days. If this usage question has evolved into a feature request or docs update, please remove the 'Type: usage' label and add the 'Type: enhancement' label instead.

github-actions[bot] avatar Nov 18 '25 11:11 github-actions[bot]