Release Notes 4.12

What’s New

ArcGIS Enterprise 10.6.0 Support

From this version on, compliance to ArcGIS Enterprise 10.6.0 is ensured.

Groupadministration

Group administration has been comprehensively expanded. Group administrators now have the option of defining roles that are only visible and usable within their own group. This means that roles that were not created within their own group are no longer visible to group administrators. Furthermore, it is now possible to bind roles not only to specific users, but also to groups. Group administrators can now also assign authorizations to other groups, and a new granularity level for role assignment has been created for super administrators.

Update Notes

This section describes changes to be considered when updating to this version from the prior version.

When updating from a previous version to this version, also read the "Update Notes" of all intermediate releases. For any update note you need to check if it applies to your setup and act accordingly.

The database schema was changed with the previous version 4.11 as well. So if you are upgrading from a version before 4.11, you have to follow the steps described in 4.11 > Update Notes before migrating to 4.12.

This section describes the required update of an existing security.manager database to version 4.12. These instructions apply if you are updating from any security.manager version starting from 4.11.0.

The existing database schema used by this product as well as its tables and data can still be used. The schema, however, needs to be updated as described in the following.

Updating Prerequisites

  • A database user with according grants to create tables and indexes

  • A database client to run an SQL script

  • Access to the SQL migration script available in [UNPACK_FOLDER]/security.manager/software/sql/upgrade/4.11-4.12

Update Database Schema

An update from a version prior to 4.12.0 requires the creation of a new table.

  1. Stop Tomcat running security.manager

  2. As a database user with according grants, run the script [UNPACK_FOLDER]/security.manager/software/sql/upgrade/4.11-4.12/[DBMS]-schema-changes.sql as appropriate to your actual DBMS type.

  3. Check if the table was created in the schema that contains the other security.manager tables.

  4. Start Tomcat

Changelog

4.12.0

New Features and Improvements

[SECMAN‑1625]

Default password hash algorithm changed to SHA-512

[SECMAN‑1612]

Respect JSONP callback parameter for /generateToken requests

[SECMAN‑1611]

Support for "application/javascript" in URL Interceptor

[SECMAN‑1610]

Forward to returnURL on /account/login failure

[SECMAN‑1607]

Don’t display drop down box if only one group can be selected

[SECMAN‑1594]

Provide for accepting terms of use during self-registration

[SECMAN‑1583]

Allow group admins to create roles and assign them to groups of users

[SECMAN‑1557]

ArcGIS 10.6.0 compliance

[SECMAN‑1314]

In installer exclusively offer SHA-2 and/or SHA-3 hashing for passwords

Fixed Issues

[SECMAN‑1620]

Logout button not displayed

[SECMAN‑1618]

Hidden fields can be returned on /query operation

[SECMAN‑1609]

User can be created without password

[SECMAN‑1603]

Interference of concurrent group admin and super admin sessions in policy manager

[SECMAN‑1602]

Some installer .sh scripts have Windows line endings (CRLF)

[SECMAN‑1591]

MapServer identify operation not working

[SECMAN‑1579]

Operation /addAttachment with multipart POST request fails when using Jersey client implementation

[SECMAN‑1485]

Button to add features to spatial obligation is too small

[SECMAN‑1458]

HTML is not escaped for feature values

[SECMAN‑1316]

Do not add user 'Administrator' by default

[SECMAN‑1315]

Installer suggests default password for 'smadmin'

[SECMAN‑1204]

Cannot change user password using PostgreSQL driver 9.4 1202 JDBC 41 or 9.4 1201 JDBC 42 and higher