GeekInTheNorth / GeekInTheNorth/Stott.Security.Optimizely

[Permissions Policy] Add support for Permissions-Policy-Report-Only and Reporting URL

Open
#383 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement Under Consideration
Dominant language
C#
Stars
11
Forks
6
PR merge metrics
No merged PRs in 30d

Description

The Permission Policy header is currently only active or absent. There is no mechanism to allow it to be used in a report only mode.

  • Update the Permission Policy Settings so that the Permission Policy can either be:
    • Enabled
    • Enabled (Report Only)
    • Disabled
  • Add a new setting for Permission Policy Report Uri
    • This should only allow valid URLs
    • Validation should include sending a test report to the endpoint to see if it returns a 200 response
  • Update Header generation to conditionally output the permission policy header as either:
    • Permissions-Policy
    • Permissions-Policy-Report-Only
  • Update Header generation to conditionally include the reporting definition
  • Update the report-to header to include an additional group for the Permission-Policy reporting URI

See Discussion
See Specification

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by locating the Permission Policy Settings and header-generation entry points, then read Discussion 380 and the linked Permissions-Policy-Report-Only specification. Implement the three policy states, reporting URI validation with a test request, conditional headers, and the additional report-to group; done means all requested settings and headers behave as described.

Written by the indexing model from the issue text.

Assessment

Tech stack
csharp
Domain
security
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
55/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.