radius-project / radius-project/docs
update dashboard documents to include threat model related action items
Nobody has claimed this yet.
- Dominant language
- Bicep
- Stars
- 26
- Forks
- 52
- Avg merge
- 3d 2h
- Merged PRs (30d)
- 3
Description
Currently, we can access the application on http but since we only access the application on localhost using Kubernetes port-forward. We should provide Radius documentation that captures below guidelines to be followed if/when a customer chooses to allow Dashboard access to multiple users and/ or make dashboard public facing.
-
Dashboard should be accessed only on HTTPS if it should be available outside cluster.
-
Enable authentication on Dashboard. This could be tied to RBAC support on Radius, since we might want the same users to be allowed dashboard logins by default with permissions configured using Backstage permission system.
-
The Backstage permissions system should be enabled and configured to restrict access as necessary.
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 locating the existing Radius Dashboard documentation and any pages covering external access, authentication, RBAC, or Backstage permissions. Add the three listed threat-model action items, including HTTPS, authentication, and permission restrictions, and verify that the guidance clearly addresses multi-user or public-facing dashboard access.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kubernetes
- Domain
- authentication, authorization, documentation, security
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100