Project-level authorization settings
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 37.4k
- Forks
- 3k
- Avg merge
- 1d 3h
- Merged PRs (30d)
- 73
Description
What problem will this feature address?
Basic auth security settings right now work on application-level. If I have multiple applications in my project I want to protect with the save Basic auth settings, I have to copy-paste the settings to each project. Mildly frustating when I want to change the password a lot of applications.
Describe the solution you'd like
At least Project-based basic auth settings, identifiable by a name.
Could also have:
- Toggle to auto-apply auth settings to all project applications, including newly configured applications.
- Instance-wide auth settings
Describe alternatives you've considered
This is already possible with the via Traefik File System dynamic/middlewares.yml, but is not user-friendly.
Additional context
I guess this fits in with #274.
Will you send a PR to implement it?
Yes
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
Start by tracing the existing application-level Basic auth settings and the Traefik middleware configuration referenced in dynamic/middlewares.yml. Review related issue #274 before narrowing the project-level scope, including named settings and optional propagation to current and newly configured applications. Done means the project-level behavior and its configuration flow are clearly implemented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- authentication, devops
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100