The October 2026 release of Administrator includes the following changed behavior.
Downloading metering data using REST API
When you use the version 3 metering resource to download usage data, the REST API can’t export a ZIP file greater than 50 MB.
Previously there was no size limit, which could cause OutOfMemory errors.
Elastic RTE Manager role
We renamed the existing Elastic RTE Manager role, which was previously named Elastic RTE Dev Ops Engineer.
Field name changes in ClusterConfig API calls
In ClusterConfig API calls, the following field names were changed in the systemDiskConfig and dataDisksConfig objects:
•sourceMount is now sourceFilePath
•targetMount is now projectedFilePath
Fingerprint authentication always on
IDMC performs a fingerprint authentication check every time a Secure Agent starts up and sends an alert to the notifications tray when there’s a mismatch.
Previously, you could turn off fingerprint authentication checks and IDMC sent mismatch alerts by email only.
Git repository verification
When you use an on-premise Git repository for source control, IDMC saves a local copy of the repository. To ensure that the correct repository is used, IDMC now verifies that the saved copy matches the repository that you request during a source control operation.
After the October 2026 upgrade, the first time you connect to a repository that was saved before the upgrade, IDMC creates a fresh copy instead of reusing the cached repository. This process can take extra time depending on the size of the repository and your network speed. Subsequent connections use the new copy as usual. IDMC doesn't delete the old saved copies automatically. Administrators can clear the old copies from the cache to free up disk space.
Master node requirements for elastic runtime environments
To set up an elastic runtime environment, the master node needs 60 GB of free disk space to account for additional libraries. Previously, the master node needed 50 GB.
Multi-factor authentication by default
IDMC enables multi-factor authentication by default for native human users in new organizations.
OData query parameter restrictions
If you have custom scripts or integrations that call OData endpoints directly, note that new restrictions apply to the following query parameters:
•$top, which limits the number of records returned per request
•$select, which controls which fields are returned
Note:
This change doesn’t affect use of IDMC APIs. The IDMC REST API has its own independent limits which are not changed
Review the restrictions below to avoid HTTP 400 errors or unexpected result truncation after the upgrade to the October 2026 release:
$select=* is no longer accepted
Requests that use $select=* to retrieve all fields now return an HTTP 400 error. This applies to all OData entities with no exceptions. Replace $select=* with an explicit list of the fields your integration requires. For example, use $select=id,name instead of $select=*.
$top values are subject to per-entity maximums
Each OData entity now has a configured maximum number of records that a single request can retrieve. If your request specifies a $top value that exceeds this maximum, the request might return a truncated result set or fail with an HTTP 400 error, depending on the enforcement configuration applied to that entity. In most cases, requests that omit $top are also capped to the entity maximum. Previously, many requests without an explicit $top returned the full result set. Review $top values in your queries. If your integration relies on receiving a complete, unpaginated result set by omitting $top, update it to use pagination or an explicit $top value within the entity limit.
The following data types are unaffected by this change:
•Job log entries
•Audit log entries
•Notification messages
•Users and groups
Password confirmation for email updates
When users update their email address, they are now required to enter their current password to initiate the change.
Previously, no password confirmation was needed to update an account's email address.
Resetting users
You can reset disabled SAML users who were not provisioned using SCIM.
Previously, the option to reset a user wasn't available for organizations configured to use SAML.
Scraping Secure Agent details
The Secure Agent details page changed in the October 2026 release. If you employed web scraping to extract information from this page, you must update the scraping script for the new user interface.