Skip to main content

Release r202511

What's New​

This release introduces the following enhancement:

OAuth 2.0 Authentication for Services​

Previously, service endpoints could be either

  • public, or
  • protected by Basic Authentication.

With this release, service endpoints can now also be secured using OAuth 2.0, specifically the Client Credentials Grant flow as defined in RFC 6749, Section 4.4.

When a service is protected with OAuth 2.0, external applications must:

  1. Obtain an access token using valid OAuth credentials
  2. Include the token in the Authorization header when calling the service
  3. Refresh the token before it expires (tokens are valid for 1 hour)

For detailed setup instructions, see the automator Help documentation.

Important​

This release contains no important updates.

Timeline​

The deployments of the release will be performed on

EnvironmentDate
DemoFriday, November 28th
ProductionThursday, December 4th

The deployment of the Production environments will be conducted outside of office hours (Central European Time Zone).