Skip to content

v7.9-beta.6

Pre-release
Pre-release
Compare
Choose a tag to compare
@github-actions github-actions released this 07 Apr 16:41
· 31 commits to master since this release
v7.9-beta.6
064362a

v7.9-beta.6

  • Issue #4109 : Add receive config properties x509CertificateHeader, x509CertificateDnHeader and allowedCertificateProviders to control the use of certificates and DNs placed in the request headers by load balancers or reverse proxies that are doing the TLS termination. Header keys were previously hard coded. allowedCertificateProviders is an allow list of FQDN/IPs that are allowed to use the cert/DN headers.

  • Add Dropwizard Metrics to proxy.

  • Change proxy to use the same caching as stroom.

  • Remove unused proxy config property maxAggregateAge. aggregationFrequency controls the aggregation age/frequency.

  • Stroom-Proxy instances that are making remote feed status requests using an API key or token, will now need to hold the application permission Check Receipt Status in Stroom. This prevents anybody with an API key from checking feed statuses.

  • Issue #4312 : Add Data Feed Keys to proxy and stroom to allow their use in data receipt authentication. Replace proxyConfig.receive.(certificateAuthenticationEnabled|tokenAuthenticationEnabled) with proxyConfig.receive.enabledAuthenticationTypes that takes values: DATA_FEED_KEY|TOKEN|CERTIFICATE (where TOKEN means an oauth token or an API key). The feed status check endpoint /api/feedStatus/v1 has been deprecated. Proxies with a version >=v7.9 should now use /api/feedStatus/v2.

  • Replace proxy config prop proxyConfig.eventStore.maxOpenFiles with proxyConfig.eventStore.openFilesCache.

  • Add optional auto-generation of the Feed attribute using property proxyConfig.receive.feedNameGenerationEnabled. This is used alongside properties proxyConfig.receive.feedNameTemplate (which defines a template for the auto-generated feed name using meta keys and their values) and feedNameGenerationMandatoryHeaders which defines the mandatory meta headers that must be present for a auto-generation of the feed name to be possible.

  • Add a new Content Templates screen to stroom (requires Manage Content Templates application permission). This screen is used to define rules for matching incoming data where the feed does not exist and creating content to process data for that feed.

  • Feed status check calls made by a proxy into stroom now require the application permission Check Receipt Status. This is to stop anyone with an API key from discovering the feeds available in stroom. Any existing API keys used for feed status checks on proxy will need to have Check Receipt Status granted to the owner of the key.

  • Issue #4844 : Fix issue where vis parent table filters are not applied to the right data values.

Assets 20
Loading