datafusion-contrib / datafusion-contrib/datafusion-postgres
Revisit AuthManager design
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 160
- Forks
- 44
- Avg merge
- 1d 4h
- Merged PRs (30d)
- 14
Description
Currently we have AuthManager as a basic gateway to authn and authz. In #186 , it also opens a connection between AuthManager and pg_catalog, which may block #189 .
I haven't got a clear idea for myself at what scope we have support for authn/authz in this library. This ideal situation is user can bring their own StartupHandler for authn, while use a decorator or interceptor for query handlers to archive authz. This approach will discouple auth concept completely from this library so we can make this library solid and generic enough for its core features.
Let me know about your ideas.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading the AuthManager design described here and the related issues #186 and #189, including the pg_catalog connection. Then evaluate the proposed StartupHandler and decorator or interceptor boundaries for authn and authz. Done requires an agreed scope and design for decoupling authentication and authorization from the library.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- postgresql, rust
- Domain
- authentication, authorization, backend-api-design
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100