Release Notes 4.11
Update Notes
Configuration Changes
- security.user.username.regexpr
-
The default value of the configuration property
security.user.username.regexprwas changed (see System hardening). Before this change, usernames were allowed to contain spaces, which is prohibited now. If you override this property in yourapplication.propertiesfile, adopt this behavior.
Database Changes
This section describes the required update of an existing security.manager database to version 4.11. These instructions apply if you are updating from any security.manager version starting from 4.4.0 up to 4.11.1.
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 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.4-4.11
Update Database Schema
An update from a version prior to 4.11.0 requires the creation of a new table and an index for that table.
-
Stop Tomcat running security.manager
-
As a database user with according grants, run the script
[UNPACK_FOLDER]/security.manager/software/sql/upgrade/4.4-4.11/[DBMS]-schema-changes.sqlas appropriate to your actual DBMS type. -
Check if the table and index was created in the schema that contains the other security.manager tables.
-
Start Tomcat