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