Skip to content

Release v19.96.0

Choose a tag to compare

@github-actions github-actions released this 20 Oct 02:33
8deb2c4

The Chronicle server can now authenticate the calls it makes to an HTTP storage connection resolver, using OAuth client credentials or Microsoft Entra ID (including managed identities), in addition to a static bearer header. See Authenticate the resolver.

Added

  • authentication settings on the HTTP storage connection resolver: ClientCredentials (token endpoint, client id, secret and scope) and AzureCredential (managed identity, workload identity or default Azure credential, with a scope). Resolvers configured without authentication behave as before (#5154)

Changed

  • The Chronicle server now uses Cratis Arc 22.131.0 (#5154)
  • Validation failures returned by the server's management commands now report member names in camelCase (for example name instead of Name), matching Arc's validation contract (#5154)