v0.5.17

[SanjayVas]

This promotes v0.5.17-rc1

Highlights

• The Reporting public API now uses the Access API for all authorization checks.
• The Reporting public API server accepts an RFC 9068 OAuth access token credentials as an alternative to a client (mTLS) certificate.
  • This requires passing --require-client-auth=false to the Reporting public API server.
• The Halo Kubernetes object configuration for the Reporting system now includes a grpc-gateway instance for the Reporting public API, running on the standard HTTPS port 443 on the same load balancer address.
  • This relies on using OAuth access tokens for Reporting API server authentication.
  • See the updated deployment guide.

Potentially Requiring Action

• The proxied DataProviders and EventGroupMetadataDescriptors services in the Reporting public API server use a fixed MC's credentials to call the Kingdom. This can be controlled by the --system-measurement-consumer option to the Reporting public API server.
• The Reporting public API server has a new required --open-id-providers-config-file option.
  • In the Halo test environment configuration, this comes from the open_id_providers_config.json file in the config-files ConfigMap. See the updated deployment guide.
• MeasurementConsumerConfig has a new offline_principal field. This must be specified in order for Report scheduling to occur for a given MeasurementConsumer.
  • The Report scheduling feature has not seen much use, so this is mentioned only for completeness.

What's Changed

• feat!: Use Access API for Reporting service authorization by @SanjayVas in feat!: Use Access API for Reporting service authorization #2020
• feat!: Accept RFC 9068 OAuth tokens as Reporting API credentials by @SanjayVas in feat!: Accept RFC 9068 OAuth tokens as Reporting API credentials #2063
• feat: Add grpc-gateway for Reporting API by @SanjayVas in feat: Add grpc-gateway for Reporting API #2048

Full Changelog: v0.5.16...v0.5.17

---

This discussion was created from the release v0.5.17.