Known issues

This section is intended to contain the list of known issues that are not quick to solve i.e. those that occur in included libraries. If possible there is a workaround to the issue. This list does not replace the bugtracking tool for CzechIdM - https://redmine.czechidm.com

For the most common support requests, see this wiki page - https://wiki.czechidm.com/priv/procesy_bcv/caste_supportni_pozadavky?s[]=%2Adisk%2A

You can face this issue, during upgrading IdM version. During start up when the change scripts are executed some of them is "skipped" but there is no error and you will notice it later, when you try to use some IdM function which is relying on this change script. This issue was found during upgrade from 9.4 to 9.7.14 and the missing change scripts are from CORE V9\_06\_002 and V9\_06\_003 and as result, role assigning failed on server error, because of missing column. Change script V9\_06\_001 was executed correctly and change script from 9.7.x was executed correctly to.

If you want to be sure, after you upgrade IdM look into database table idm\_schema\_MODULENAME and check against repository that all change script are there. If you found some of them is missing just run the change script manually directly in DB.

Affected IdM version: 12.x.x

If there is an EAV codelist attribute for IdmIdentity and we want to create an automatic role based on the attribute then we are not able to set this rule. Basically the green button "Set" (Roles » Automatic roles » Based On The Attribute » Add request for automatic role) will not do anything when applying the rule. This issue has been fixed in version 13.0.1

Affected IdM version: 14.3.0

An update in policies caused an error in resetting user's password if the user's first name or last name is empty. This operation throws INTERNAL_SERVER_ERROR: Cannot invoke "String.toLowerCase()" because the return value of "eu.bcvsolutions.idm.core.api.dto.IdmIdentityDto.getLastName()" is null ({}). This issue has also been fixed for version 14.2.x.

A configuration in IdM has been added, which fixes the password reset behaviour (enabled in Settings » Configuration):

idm.sec.core.identity.passwordChange.validateBannedStrings=true

Ticket: https://redmine.bcvsolutions.eu/issues/34415

If the ticket above is not closed, then the issue is still relevant. Basically if we change "-r0" to "-r1" (release) on the line image: repo.iamappliance.com:8445/bcv-czechidm:12.3.3-r0 in /data/registry/node-active-config/docker-compose-czechidm.yml, we will encounter issues with connector server (e.g. unable to load Exchange account in IdM). The solution is to have "-r0" or if the ticket above is resolved, then "-r2".

This is not a problem of IdM but rather of office products (we use mostly LibreOffice). Data in a column are not fully displayed. If we double click the cell, it reveals all data stored in it. We've faced "refunds" from customers and so far we've solved it by uploading a report to google drive, where it is displayed correctly. The solution for this is to format the whole column (from numbers to text) and it should reveal data correctly.

Note: On newer versions of LibreOffice the issue hasn't been encountered, so it can be caused by older versions.

After updating the operating system, some docker containers fail to start. The quickest solution is to drop the affected container and recreate it (commands below):

systemctl stop <service>        // stop the affected service, e.g. iam-czehcidm
docker ps -a                    // list all docker containers to find the affected container that we want to drop and recreate
docker rm <container>           // remove the container
systemctl start <service>       // start the affected service to recreate the container

The issue is caused by an incompatibility between Docker Composer and the Docker daemon. This issue has been dealt with in this ticket: https://redmine.bcvsolutions.eu/issues/29415