Use a Policy for Auth Access to Profile etc.
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 45/100
- Issue type
- Refactor
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- csharp
- Domain
- authorization
Research direction
Start with the ASP.NET Core authorization policies documentation linked in the issue, then inspect the pages under /Pages/Profile and their existing [Authorize] attributes. Identify how access is currently duplicated and define done as applying one policy-based approach to everything under /Pages/Profile without that duplication.
Written by the indexing model from the issue text.
Description
See: https://docs.microsoft.com/en-us/aspnet/core/security/authorization/policies?view=aspnetcore-5.0
Address authentication for everything under /Pages/Profile to eliminate duplication of [Authorize] attribute.
- Dominant language
- C#
- Stars
- 157
- Forks
- 59
- Avg merge
- 3h 12m
- Merged PRs (30d)
- 4
Getting set up
- Ships a Dockerfile or Docker Compose file
- No pull request template
- Read the contributing 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.
More from DevBetterCom/DevBetterWeb
-
Remove duplicate Vimeo DI registration; use NimblePros.Vimeo AddVimeoServices and upgrade packageOpen
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
DevBetterCom/DevBetterWeb#1486 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 5/5 Over a week Newbie friendliness 35/100
DevBetterCom/DevBetterWeb#1472 ·
Maintainers usually reply within 1 day
-
Difficulty 4/5 3-5 days Newbie friendliness 20/100
DevBetterCom/DevBetterWeb#1393 ·
Maintainers usually reply within 1 day
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
DevBetterCom/DevBetterWeb#1392 ·
Maintainers usually reply within 1 day
-
.NET enhancement
Difficulty 5/5 Over a week Newbie friendliness 35/100
DevBetterCom/DevBetterWeb#1380 ·
Maintainers usually reply within 1 day
All issues in DevBetterCom/DevBetterWeb
Similar issues
-
area-NavigationView bug needs-triage team-Controls
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
microsoft/microsoft-ui-xaml#12671 · 3 comments ·
Maintainers usually reply within 2 days
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Maintainers usually reply within 1 day
-
Improve time codes: status hint doesn't mention the new Shift+F7 / Shift+F8 "to check" navigationOpen
Difficulty 1/5 Under an hour Newbie friendliness 88/100
SubtitleEdit/subtitleedit#16943 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
elsa-workflows/elsa-core#9273 ·
Maintainers usually reply within 1 day