mirror of
https://github.com/elastic/kibana.git
synced 2025-04-25 02:09:32 -04:00
cc50c8dc94
## Summary
1. Added top-level `permissionsPolicy` configuration setting.
2. Added support for `report_to` directive.
3. Added support for `Permissions-Policy-Report-Only` header to enable
reporting mode.
4. The [spec](https://www.w3.org/TR/permissions-policy/#reporting)
mentions `featureId` in the reporting body, however the field is
`policyId` in Chromium.
## How to test
- Add in your `kibana.dev.yml`.
```
server.customResponseHeaders.Reporting-Endpoints: violations-endpoint="https://localhost:5601/kibana/internal/security/analytics/_record_violations"
server.securityResponseHeaders.permissionsPolicy: 'microphone=()'
server.securityResponseHeaders.permissionsPolicyReportOnly: 'camera=()'
```
- Make sure you have [dev tools configured for Reporting
API](https://developer.chrome.com/docs/capabilities/web-apis/reporting-api#use_devtools).
- In the browser console invoke `navigator.mediaDevices.getUserMedia({
audio: true, video: true }).catch((e) => {});`
- Open Dev Tools -> Application -> Reporting API.
You should see 2 reports for permissions violation, one with `report`
disposition and another with `enforce` disposition.
<img width="1285" alt="Screenshot 2024-06-27 at 13 36 12"
src="
|
||
|---|---|---|
| .. | ||
| images | ||
| install | ||
| upgrade | ||
| access.asciidoc | ||
| configuring-logging.asciidoc | ||
| configuring-reporting.asciidoc | ||
| connect-to-elasticsearch.asciidoc | ||
| docker.asciidoc | ||
| install.asciidoc | ||
| secure-settings.asciidoc | ||
| settings.asciidoc | ||
| start-stop.asciidoc | ||
| upgrade.asciidoc | ||