Release Notes 1.10
What’s New
Branch Versioning support
security.manager NEXT now supports enforcing policies on branch versioned data. Please note that working with branch versions under restricted permissions may differ from the usual workflow. Please refer to the Version Management Server section under Limitations for more details.
Update Notes
If you skip several versions during the update, please also follow all update notes of the intervening versions. |
Dropped support of ArcGIS Enterprise 10.9.0
ArcGIS Enterprise versions up to 10.9.0 are no longer supported.
security.manager NEXT CLI
The additional .node
file is no longer required for the Windows version of secmanctl.exe. This file was removed in version 1.10.1.
Manager UI and use of untrusted certificates
HTTPS requests to ArcGIS Server or portal may be forwarded by the Manager UI via an internal proxy.
Since this version of security.manager NEXT, the internal proxy no longer accepts untrusted certificates by default.
This applies in particular to HTTPS connections to ArcGIS Enterprise endpoints on ports 6443 and 7443, which are configured with self-signed certificates by default.
In order to continue using untrusted certificates in connection with the internal proxy, especially in test environments, you must now set the configuration option security.ssl.trustAny=true
in the application.properties
.
Failure to do so may result in error messages about failed requests in the Manager UI.
Warnings
OGC API Features
With ArcGIS 11.x, on services with activated security.manager NEXT, unauthorized layer information can be exposed via the OGC API Features endpoint. Please deactivate OGC API Features on those services.
Further information can be found at Limitations.
Changelog
1.10.0
Fixed Security Issues
|
New Features
|
Improve unclear display name for webapp |
|
Support branch versioning |
|
Regard historicMoment parameter in feature queries |
Fixed Issues
|
[secmanctl] Metadata validation reports warning for service with group layer |
|
[secmanctl] Metadata validation reports warning for service with raster layer |
|
Parsing of layer parameter during a /dynamiclayer/query request, with null renderer leads to error |
|
ArcGIS Pro fails to split features on SQL Server-based feature service when spatial restriction is active |
|
ArcGIS Pro fails to split feature on version-enabled feature service with an active spatial restriction |
|
ArcGIS Pro fails to split feature on version-enabled feature service when restriction is active |