Overview of all update notes
1.6
Support for Java 17 discontinued
This version of the Identity Service no longer supports Java 17. Use Java 21 or Java 25 instead.
Changes to configuration parameters
configuration.watch.changes-
The configuration parameter
configuration.watch.changeshas been removed. Changes to the configuration during runtime are no longer supported.If you set this configuration parameter in the file
application.properties, you can remove it. security.oauth.tokenRules.addDefaults-
The configuration parameter
security.oauth.tokenRules.addDefaultsnow has the default valuefalse. As a result, the Identity Service no longer registers the configured identity provider as a trusted service. The use of this configuration parameter is no longer recommended and will be removed in future versions.If you have set
security.oauth.providertoarcgis, add ArcGIS Enterprise Portal or ArcGIS Online as a trusted service. If you have setsecurity.oauth.providertokeycloak, add your Keycloak server as a trusted service. Examples can be found under Trusted services.
1.5
Support ArcGIS Enterprise
With this release of Identity Services, ArcGIS Enterprise 11.2 and 11.3 are supported.
Database schema changes
The database schema has been updated in this version.
The columns IDENT_TOKENS.TOKEN_KEY and IDENT_EXTSESSIONS.EXTSTATE have been reduced in length to avoid warnings on certain databases.
The recommended approach to apply these changes is to let Identity Service recreate the required database tables from scratch:
-
The database user must have permissions to create/alter tables and indices.
-
After the update these permissions can be revoked again.
To perform the update, proceed manually:
-
Drop the existing tables. If you use a dedicated database only for Identity Service, you can alternatively drop the entire database. (Note: both approaches will drop existing user sessions).
To drop the existing tables, use the appropriate SQL script for your database:
-
Start Identity Service with
db.hibernate.schemaUpdateset toupdate(this is the default). This will recreate the required database schema. Alternatively, you can recreate the database schema by running the appropriate SQL script included with the product distribution.