stackql / stackql/stackql-devel
[FEATURE] Multi-user stackql servers
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 0
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
Feature Description
For mature stackql servers:
- IAM; user and role semantics.
- multiple users and coupling of server sessions to IAM.
- mTLS and/or password auth flows.
- table, column, row security TBA.
Example(s)
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
Possible Approaches or Libraries to Consider
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.
Contributor guide
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
No files, tests, or entry points are named. Start by defining the IAM, user and role semantics, session coupling, and mTLS or password authentication scope; table, column, and row security are explicitly marked TBA. Done would require an agreed design and implementation plan for the selected scope.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- authentication, authorization, backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 15/100