logoBack to home screen

ADx 2.5.284 (10/2/2021) Release Notes

This is a patch release to ADx 2.5. Here's a list of new features and issue fixes:

  • When using an ADx integration with Okta, changing a user's role in Okta is now automatically updated in ADx. For the update to be visible, the user must log out and re-log in to ADx.
  • Some errors occurred when calling the merge-templates request. These errors have been resolved.
  • Previously, video previews were scaled down. Video previews are displayed in full size now.

Java Version

This release was tested with JDK 11 JDK-11.0.9.1-zulu11.43.55.

Runtime Properties and Configuration changes

No runtime properties have been added, changed or removed in this release.

List of New Features and Improvements

No new features in this patch release.

Bug Fixes

IssuePrioritySummary Description
AD-2051CriticalError on merge-template. TextTemplateToTextJob is not clob.
AD-2025MajorImprove support for Okta integration / mainly role handling
CSWR-59MajorEnable access groups and roles for SSO
AD-2052MajorCreate full size teaser video instead of scaled down version

Updating Conversion and ADx

For information on how to update previously installed Conversion and ADx, see the following:

Known Issues

Below you can find a list of problems we're still working on.

Known Issues ADx

TicketSEVERITYDescription
https://jira.braintribe.com/browse/AD-321CRITICALAdd missing indices
https://jira.braintribe.com/browse/AD-348MAJORADx Admin: Repository Modification-Status not updated on Update
https://jira.braintribe.com/browse/AD-1898MAJORMin and Max length metadata not respected on initial upload
https://jira.braintribe.com/browse/AD-342MINORHibernate warnings in the log files
https://jira.braintribe.com/browse/AD-341MINORJava warnings during for Java 9 and later
https://jira.braintribe.com/browse/AD-311MINOROracle - DbLockManager prints Oracle constraint message

Reimporting an Existing Repository Requires UI Reload

In some cases, when reimporting an existing repository, repository properties are not rendered correctly. To make sure properties are rendered correctly, refresh your browser after each import.

Cannot migrate legacy contents simultaneously

Due to cache database being shared between repositories, it's not possible for now to run multiple migration jobs from a single legacy repository at the same time. You need to wait for the previous migration to finish before running a new one.

Min and Max length metadata not respected on initial upload

String length checks are only applied when values are updated but not on the initial upload.

Known Issues Conversion

TicketSEVERITYDescription
https://jira.braintribe.com/browse/AD-338CRITICALIntroduce roles for conversion
https://jira.braintribe.com/browse/AD-337MAJORMake TF Conversion workbench consistent to ADx

https://jira.braintribe.com/browse/EXTDOCS-71 | MINOR | Fix wrong encoding on opening resource in Browser |

Minor Warnings

StatusLogger Error

The following error currently appears in ADx console output. It doesn't affect ADx functionality or performance.

ERROR StatusLogger No log4j2 configuration file found. Using default configuration: logging only errors to the console.
  Set system property 'org.apache.logging.log4j.simplelog.StatusLogger.level' to TRACE to show Log4j2 internal initialization logging.

Tomcat Shutdown Warning

The following warning is sometimes thrown by Tomcat when stopping the service:

./tribefire-console-stop.sh
...
Tomcat did not stop in time.
PID file was not removed.
To aid diagnostics a thread dump has been written to standard out.
Tribefire Host stopped.

This happens when shutdown takes longer than Tomcat expects. Shutdown may take several minutes, which will result in this message being printed out. This warning could appear on both Conversion and ADx.

Java Warnings

When using Java 9 or later, the following warning may appear in application logs and also during installation procedure:

WARNING: An illegal reflective access operation has occurred
WARNING	: Illegal reflective access by com.braintribe.model.processing.itw.asm.AsmClassLoaderWrapper$1 (file:/path/to/instant-type-weaving-1.0.28.jar) to method java.lang.ClassLoader.defineClass(java.lang.String,byte[],int,int)
WARNING: Please consider reporting this to the maintainers of com.braintribe.model.processing.itw.asm.AsmClassLoaderWrapper$1
WARNING: Use --illegal-access=warn to enable warnings of further illegal reflective access operations
WARNING: All illegal access operations will be denied in a future release

Ticket: https://jira.braintribe.com/browse/AD-341

Hibernate Warnings

The log files may contain Hibernate-related warnings. They can be identified based on the fully qualified class which starts with org.hibernate, as in:

WARNING org.hibernate.tuple.entity.EntityMetamodel 'HHH000084: Entity [com.braintribe.model.user.User] is abstract-class/interface explicitly mapped as non-abstract; be sure to supply entity-names' [TribefireServices-2.0:tribefire-services#initialize,ApplicationLoader:/tribefire-services#initialize]

Ticket: https://jira.braintribe.com/browse/AD-342

These warnings do not affect the functionality of the application and can be ignored. We are working on a fix.