PIP 6.1.0 Release Notes
June 14th 2022
The new release of PhenixID Identity Provisioning (PIP) improves the stability, compatibility and security of your solution, and is recommended for all installations.
Updated external tools
1. Converting log settings
The tool for converting the log settings from PIP versions prior to 6.0.0 to the log4j2.xml format used in PIP 6.0.0 has been updated. The tool will now handle special characters used in the log file name. It also provides more options when making the conversion.
Read more in PSD1197.
1. Log configuration
From this version it is possible to make some basic configuration for the log settings from inside the PIP Configurator. The changes in the log settings will be saved directly in the log4j2.xml file. For any advanced configuration, the settings are made directly in the log4j2.xml file.
Read more in PSD1192.
2. Export and import of log configuration
When exporting a policy with policy specific logging, the corresponding log settings in the log4j2.xml file will be exported as well.
When importing a policy with policy specific logging, the log settings will appear as a separate object in the list of import objects.
Read more in PSD1192.
New or updated features
1. Support for SESSION in condition
When using the condition filter of type multiple in a Run action or when setting a condition for an action in a policy, SESSION() can be used in the condition. If the session attribute entered in SESSION() is a multivalue, only the first value for the attribute will be used in the condition.
2. Transaction number in log
The transaction number, unique for every running policy, is now added to the message in the log. This makes it easier to read the log file when multiple policies are running parallell.
3. Unique transaction numbers
The transaction numbers are now unique for every policy that is running. In previous version the transaction number was only unique for the scheduler, but the same for the policies running in the same scheduler.
4. Policy logging of no logger
If a policy have a policy specific logger configured, but the corresponding logger does not exist in the log4j2.xml file, the policy log will now be written in the service log or the configurator log instead.
1. Test LDAP Connection
In PIP 6.0.2, an exception occurred when using the ‘Test LDAP Connection’ button at an LDAP datasource. This has been fixed.
2. Null values in simple filter
In PIP 6.0.1, we fixed the problem with session attributes sometimes having null values. This resulted in problems for the simple filter in Run actions, which have now been solved.
3. Lost connection in LDAP
When trying to make a connection to a LDAP directory that is not available, PIP makes 5 attempts before it considers the directory unavailable. Sometimes, PIP could get stuck during the connection attempt, and the policy did not continue until PIP was restarted. This has now been fixed by also adding a time limit for the connection attempt.
Identity Provisioning is now tested and bundled with java 17.0.0_35 from Azul.
2. Upgrade verifications
Verify so there are no duplicate jar-files, as this might cause an unexpected behavior.
Compare /lib with /ext. If duplicates exists, make sure to keep the latest version of jar-files.
3. End of Support
Information about the oldest supported version can be found here.