Release Notes 4.18
Update Notes
This section describes changes to be considered when updating to this version from the prior version.
Updating from previous versions requires to carefully read and follow all intermediate "Update Notes" from the installed version to this version. |
Configuration Changes
The properties security.responseHeaders.common
and security.responseHeaders.html
were added to allow the use of additional HTTP headers.
The property security.allowed.ipranges
was added to define IP address ranges that are allowed to access secured endpoints.
Please refer to the section Security Settings for further details.
Deprecated Features
The following features are regarded as deprecated and might be removed in future:
-
Native WSS authentication protocol of the Web Security Service (WSS) component
-
(Json) Token authentication protocol of the Web Security Service (WSS) component. It is recommended to use the - currently named - "agstoken" authentication protocol instead.
-
Protection of Web Coverage Service (WCS)
-
Protection of transactional WFS (WFS-T)
-
INSPIRE View and Download Services as separate service types are maintained within the service types WMS and WFS
-
Access to protected services via Gateway application (tab "Gates" in the security.manager administration)
Known Limitations
The following list contains all limitation known at the time of the release of version 4.19.
Delayed visibility of parallel changes of users and rights by different users or external systems (eg LDAP clients) in the security.manager Administrator
To visualize changes from other users / systems in the tree displayed on the left side of the Administrator interface, simply select the root node of the tree and the reload tree button.
Evaluation of two rights
When two rights are defined that are applicable to a user, it is important to determine the correct sequence in the Security Manager administrator (in the dialog "Policy Set"). For example: It is a legal definition that all users are granted access to a WMS, but with copyright restrictions. A user might be a member of a user group "registered" where another piece of legislation for this WMS defines that the access granted WITHOUT Copyright constraint. Both of these rights are valid if the user group "registered" accesses the WMS. In this case, the first policy in the list is used. To prevent the users of the group "registered" from seeing the same copyright notice as unregistered users, this right must be uppermost in the administration set.
WFS feature types are required to have unique names
The security.manager does not distinguish feature types which have the same name but different namespaces, for example x:city
is recognized as equal to y:city
.
Therefore It is required that feature types have unique names.
Use of variable feature IDs in WFS services as a source of spatial conditions
Care must be taken of the accuracy and stability of the displayed feature IDs when using them to create spatial obligations.
Feature IDs of the form fid-4d0f905b_126c17decf6_-7d52
indicate internal auto-generated feature-IDs, which change with each new request and thus can not be used for referencing features.
If feature IDs change with each request to the WFS, this is due to a lack of feature IDs in the WFS response.
The configuration of the WFS service needs to be reviewed so that stable feature identifiers are delivered correctly.
If installed in an instance of Tomcat which does not yet contain the directory [TOMCAT_HOME]/conf/Catalina/localhost
, some configuration files are not created correctly
Alternative 1: Create the folder prior to installation.
Alternative 2: During an installation, the context.xml
files are stored in the [SECMAN_INSTALL]/postinstall
directory.
They can be simply copied into the directory [TOMCAT_HOME]/conf/Catalina/localhost
.
In the installation type container-managed database, the xml files with the suffix -jndi.xml
need to be copied.
The following files must be copied:
-
administration.xml
-
gateway.xml
-
wss.xml
Use of unofficial EPSG codes by ArcGIS Server services
Depending on their configuration, ArcGIS Server services sometimes use unofficial EPSG codes for Gauß-Krüger reference systems. These are internally mapped to the corresponding official EPSG codes, The following mappings are used:
-
EPSG:31492 → EPSG:31466
-
EPSG:31493 → EPSG:31467
-
EPSG:31494 → EPSG:31468
-
EPSG:31495 → EPSG:31469
This mapping is only applied to protected services. For the definition of spatial restrictions via a WFS, only official EPSG codes are supported.
Problem with spatial restrictions for ArcGIS Server WFS
ArcGIS Server WFS do not support multipolygons or more than one polygon within a spatial filter. Thus, spatial restrictions cannot be applied if more than one geometry are selected for this restriction or if the incoming request already contains a spatial filter.
Cookie handling with Safari browser
When using a Safari browser, repeated logins might be required. To avoid this, change the security settings to always accept cookies.
Limitation regarding Spatial Obligations for "tiled" ArcGIS Server MapServer
Support for spatial obligations with ArcGIS Server cached MapServer instances requires to use the cache storage format "Compact". If any other storage format is used spatial obligations are ignored.
WMS GetMap requests with SLD parameter blocked if layerDefs parameter would be applied
As described in "Filtering features using the layerDefs parameter in WMS requests" , layerDefs has a lower priority when SLD or SLD-BODY parameter is present and is ignored.
Printing of secured services only possible with ags-relay URLs
URLs of secured MapServer services have to be used with ags-relay URL schema:
http://[HOST]/wss/service/ags-relay/ [EndpointID]/[AUTH_SCHEME]/arcgis/rest/services/ [SERVICENAME]/MapService
HTTP chunked transfer encoding must be disabled in security.manager when securing ArcGIS geocoder
The ArcGIS Geocoding Server does not support HTTP chunked transfer encoding.
If you want to secure that service, chunked encoding must be manually disabled in the settings file of security.manager.
To do that, make sure that the property http.client.chunking
in the application.properties
file is set to false (SECMAN-658).
Spatial Obligations are not supported for INSPIRE Feature Download Services based on ArcGIS for INSPIRE
ArcGIS for INSPIRE Feature Download Services do not support Polygons in queries with spatial filters. Hence for a spatial restriction is not possible.
Invalid responses from INSPIRE Feature Download Services based on ArcGIS for INSPIRE with stored queries
ArcGIS for INSPIRE Feature Download Services might create invalid responses if a GetFeature request references multiple stored queries or contains multiple query elements.
ArcGIS Server WFS and spatial restrictions as well as OGC Filter Expressions
Access to protected ArcGIS Server-based WFS might fail when spatial obligations or OGC Filter Expression obligations are in play. Affected are ArcGIS Server versions 10.3 and higher, which don’t properly support the OGC specifications. Depending on the WFS versions requested by the client (1.0.0, 1.1.0, 2.0.0) you might encounter different error messages.
UMN MapServer WFS and spatial obligations as well as OGC Filter Expressions
The WFS 1.0.0 and 1.1.0 implementations of UMN MapServer do not support the GML versions as stated in the specifications. Because of this spatial obligations and obligations with OGC Filter Expressions are not supported.
ArcGIS Server WFS and DescribeFeatureType requests
For ArcGIS Server WFS services, DescribeFeatureType requests without listing actual FeatureTypes might lead to exceptions, if this WFS provides many FeatureTypes, or the FeatureTypes have long names.
Performance and protected services with huge number of resources
If a protected service (for example a map service) contains a huge number (> 60) of resources (for example layers) performance of service requests decreases noticeably. Consider splitting up such mapping services into several services.
HTTP Basic Authentication in ArcMap and ArcGIS Pro
When trying to load a protected service into ArcMap or ArcGIS Pro via httpauth login fails although correct credentials were specified if username or password contain non-ASCII characters like german umlauts.
ArcGIS Webadaptor with name "rest" or "services"
When the webadaptor for ArcGIS Server is named "rest" or "services" like http://[HOST]/rest/rest/services
or http://[HOST]/services/rest/services
, the ArcGIS Server cannot be protected by security.manager.
When named "rest", no policies can be created, when named "services" policies cannot be enforced.
log4j 1.2.17 vulnerable to remote code execution (CVE-2019-17571)
Some vulnerability scanning tools may complain about the log4j library. According to CVE-2019-17571 the library provides a component which is vulnerable to deserialization of untrusted data. This component is not used at all, so the vulnerability can’t be exploited.
ArcGIS Server MapServer /find
operation with large result sets and spatial obligations
In combination with spatial obligations, the MapServer /find
operation may not return all expected features.
Large result sets of the /find
operation will be capped if they exceed the server side limit of features to return.
Spatial obligations will only be applied to the capped result set.
Changelog
4.18.0
New Features and Improvements
|
- Ensure that SSO cookie appends SameSite=None if secure is true and samesite is false |
Fixed Issues
|
Attribute Field Definition is ignored for TokenService |
|
GetFeatureInfo is not supported on AGS WMS using Definition Query |
|
GroupServiceRestEndpoint - Resolving all users belonging to a group fails when amount of users is quite huge |
|
Feature Server does not get printed in custom printing service based on python |
|
User cannot log in to via IdP when sec.man acts as Service Provider |
|
Group admin permissions can be assigned to foreign groups |
|
CatalogServer request fails for folders with only non-public services |
|
Export LDAP configuration fails |
|
Set-Cookie is missing secure flag |
|
Gateway app contains unnecessary libs |
|
Cannot define attribute obligation on map service with group layers |
|
[FeatureServices] Adding Features with null-Geometry fails |
|
Binary data sent over protected service gets corrupted |