Release Notes#

2.3.0#

Error Response Enhancements#

Starting in 2.3, ESS services can provide more information in their HTTP error responses. Specifically, the ESS services follow RFC 9457 (Problem Details for HTTP APIs) and may include the fields specified in the RFC:

{
  "status": <status code>,
  "title":  "<summary>",
  "detail": "<additional description/details of the error>",
  "instance": "<OpenTelemetry Span Id>"
}

For UMA and OIDC Broker services, they continue, as in earlier versions, to follow RFC 6749 (OAuth 2.0), and the new RFC 9457 fields are added to their error response.

{
  "status": <status code>,
  "title":  "<summary>",
  "detail": "<additional description/details of the error>",
  "instance": "<OpenTelemetry Span Id>",
  "error": "<error code per RFC6749>",
  "error_description": "<optional error description per RFC6749>",
  // ...
}

For error responses to browser requests, the ESS error pages (text/html media type) display the new information.

For other error responses:

  • For services that only follow RFC 9457, the error responses return as application/problem+json media type.

  • For UMA and OIDC Broker services, RFC 6749 takes precedence over RFC 9457, and as such, the error responses return as application/json media type.

For more information, see Error Responses.

Pod Deletion via Purger Application#

Starting in 2.3, ESS includes a Purger CLI application which can be used as part of a workflow for deleting user data. This can help organizations adopting ESS to comply with legislative requirements, such as GDPR/CCPA and the right to have personal data deleted.

For more information, see Purger Application.

Access Grant Query Improvements#

Starting in 2.3, ESS includes a /query endpoint in the Access Grants Service. This provides an optimized mechanism to search and filter Verifiable Credentials (VCs) which are the serialized form of access requests and grants.

This endpoint replaces the /derive endpoint, which is now deprecated.

For more information, see /query Endpoint.

3rd-party Dependency Updates#

Starting in 2.3, various 3rd-party dependencies used by ESS have been updated. Key dependency upgrades include:

Java 21#

Starting in 2.3, ESS has upgraded to Java 21.

PostgreSQL 17#

Starting in ESS 2.3, the image reference to PostgreSQL, in Inrupt’s non-production overlay (i.e., the standalone overlay), has been upgraded from version 15 to 17. Customers who are using Inrupt’s standalone overlay need to reset their state or upgrade Postgres.

This change does NOT affect those deployments that use the production overlay (i.e., the scalable-cloud overlay). Customers using the scalable-cloud overlay use their own stateful services and are not impacted by the change.

Kafka 3.8#

Starting in 2.3, ESS has upgraded to Kafka 3.8 in the standalone overlay.

Keycloak 26#

Starting in 2.3, ESS has upgraded to Keycloak 26 in the standalone overlay.

Changelogs#

For changelogs, see 2.3 Changelogs.

On this page