The October 2026 release of Administrator includes the following important notices and upcoming changes.
Deprecated support
The following functionalities are deprecated:
Redeploying a serverless runtime environment
Effective in the October 2026 release, redeploying a serverless runtime environment is deprecated. Informatica intends to drop support for redeployment in a future release. Deprecated functionality is supported, but Informatica intends to drop support in a future release. Informatica requests that you transition to different functionality before the functionality is dropped.
To update a serverless runtime environment, stop the runtime environment, edit it, and restart it. If the runtime environment fails or encounters an error, resolve the error and save the runtime environment to automatically restart it. For more information about stopping and starting a serverless runtime environment, see New features and enhancements or Runtime Environments.
Session-based authentication
Effective in the October 2025 release, session-based authentication is deprecated. Informatica intends to drop support for session-based authentication in a future release.
Deprecated functionality is supported, but Informatica intends to drop support in a future release. Informatica requests that you transition to different functionality before the functionality is dropped.
Informatica plans to replace session IDs with JSON Web Tokens for user authentication. The organization administrator can change the authentication type used for REST API requests on the Settings page in Administrator. When the administrator enables JWT authentication, browser-based user interface communications use JWT automatically.
For REST API calls, session IDs must still be included in request headers. However, with JWT authentication, the session value carries a JWT with a fixed expiry time configured in Administrator. As a result, update REST API scripts to handle automatic re-authentication before or after the token expires. For more information, see the JWT Support Knowledge article.
Session-based authentication is the default authentication type. Sometime after the October 2026 release, JWT will be the default authentication method.
Note:
Don't enable JWT authentication if you use REST V2 Connector to call IDMC APIs.
Source control repository access using Azure DevOps OAuth
Microsoft has deprecated Azure DevOps OAuth and plans to drop support soon. If your organization uses Azure DevOps OAuth to access its source control repository, the organization needs to switch to Microsoft Entra ID OAuth to prevent source control interruptions.
Note that Azure DevOps source control isn't going away. You can still use an Azure DevOps repository. Only the application that you use for repository access is changing.
An administrator can update the organization to use Microsoft Entra ID OAuth on the Settings page in Administrator. After the administrator switches the organization's repository access to Microsoft Entra ID OAuth, users can continue to use source control without any immediate action. However, each user needs to refresh their access token before support for Azure DevOps OAuth is dropped to avoid interruption in source control access. To refresh the token, click the User icon on the toolbar and select Settings. In the Source Code Control Credentials section, click Drop Authentication and then reconfigure OAuth authentication.
Note:
After an organization switches to Microsoft Entra ID OAuth, it can't revert to using Azure DevOps OAuth.
Upcoming change
We want to let you know that starting in an upcoming release, JWT authentication token values will be limited to a maximum of 2000 characters.