Skip to main content
Feedback

Connectivity Development Release Notes for January 2026

January 31 2026

JWT Token header

New
We added these features
  • Added support for the display of a new Client Assertion Type radio button field to add via the descriptor for the Client Credentials grant type. The new field has two selectable options:
    • Client Secret
    • JWT Token

Users can continue using the Client Secret option to use a shared password, which was the default or use the JWT Token option to use a digitally-signed token for advanced security and key-based authentication. Users can also provide <helptext> to these fields in the descriptor. (CON-10685)

  • Added client-side JWT ID (jti) claim support for the existing JWT Bearer grant type and the Client Credentials grant type, only if the Client Assertion type is JWT Token. This feature enables integration with third-party services that require jti claims for authentication. The client will generate unique jti values for each JWT assertion. Typically, these are UUIDs and can be selected in the ID Claim Generator field in the OAuth 2.0 tab. (CON-10596)

  • Added support for the following opt-in JWT parameter fields: (CON-10672)

    • kid (Key ID) Header Parameter
    • x5t#S256 (X.509 Certificate SHA-256 thumbprint Header Parameter)
    • x5t (X.509 Certificate SHA-1 thumbprint)
    • jku (JWK Set URL) Header Parameter
    • x5u (X.509 URL) Header Parameter

Platform Release

January 24 2025

Bounded Service Manager

Fix
We fixed this issue
  • Fixed an issue where the bounded stop of an operation was completed prior to the listen manager beginning to shut down. This fix blocks the bounded stop of an operation until it is fully completed. This action ensures that the listen operation is completely shut down before the Listen Manager shutdown process begins. In addition, the addService operation on bounded start is being made synchronous. (CON-9750)

Connector configurations

Fix
We fixed this issue
  • Fixed an issue where users were forced to reconfigure the Start shape when changing the process mode for a listener process because the connector configurations reset the selected connector and operation components. (CON-10634)

Connector SDK

New
We added this feature

The getSslContext method is currently defined in the BrowseContext class. It has been moved to AtomContext so that the SSL context is available to all connector contexts that require a secure connection at the runtime level, which includes any operation types that do not extend BrowseContext. (CON-601)

JWT Token header

note

Subsequent to the Runtime Release, the following features have been deferred to a future release. UPDATE: These features were released on January 31, 2026.

New
We added these features
  • Added support for the display of a new Client Assertion Type radio button field to add via the descriptor for the Client Credentials grant type. The new field has two selectable options:
    • Client Secret
    • JWT Token

Users can continue using the Client Secret option to use a shared password, which was the default or use the JWT Token option to use a digitally-signed token for advanced security and key-based authentication. Users can also provide <helptext> to these fields in the descriptor. (CON-10685)

  • Added client-side JWT ID (jti) claim support for the existing JWT Bearer grant type and the Client Credentials grant type, only if the Client Assertion type is JWT Token. This feature enables integration with third-party services that require jti claims for authentication. The client will generate unique jti values for each JWT assertion. Typically, these are UUIDs and can be selected in the ID Claim Generator field in the OAuth 2.0 tab. (CON-10596)

  • Added support for the following opt-in JWT parameter fields: (CON-10672)

    • kid (Key ID) Header Parameter
    • x5t#S256 (X.509 Certificate SHA-256 thumbprint Header Parameter)
    • x5t (X.509 Certificate SHA-1 thumbprint)
    • jku (JWK Set URL) Header Parameter
    • x5u (X.509 URL) Header Parameter

OAuth 2.0 changes

New
We added this feature
  • Changes to the OAuth 2.0 tab to incorporate the new Client Assertion Type field. Users can select between Client Secret and JWT Token when defining a client assertion type. (CON-10585)
Fix
We fixed this issue

  • Fixed an issue where a NullPointerException was returned when invalid credentials were given during an OAuth 2.0 connection. An appropriate error message is now displayed for all connections that use OAuth 2.0 grant types. (CON-3112)

  • Fixed a situation where an error was thrown if elements in the descriptor file were not in a certain order. Now, descriptor elements can be in any order within the descriptor file. (CON-10723)

Selectable Profile support

New
We added these features

  • Connectors can now retrieve the request/response schema for JSON and XML profile types from a connector as an inputstream. (CON-10507)

  • Added support for request/input profiles and response/output profiles when supports browse is false. These profiles can be associated with a custom label and <helptext>. (CON-10543)

On this Page