Release Notes
Provisioning Service 4.0.0

Facts

• Product: Provisioning Service (former Automatic Account Manager)
• Platform: Any supported
• Revision History

Core updates 4.0.0 released September 29th 2016

LDAP Referral

It is now possible to choose to ignore LDAP referrals on an LDAP data source.

Schedulers

A new scheduler type is introduced, where it is possible to configure the scheduler to run at a certain minute past every hour.

A bug when using ‘Exclude Hours’ is solved.

Daylight Saving Time

When the time changes, based on daylight saving time, the schedulers with fixed time will run at the correct time.

Deprecated Actions

The actions that has been marked as deprecated since version 3.5 was released in April 2014 has now been removed. The actions are: Certificate Handler 1.5, Date Handler 2.1, Format Attribute Value 2.0 and Send SMS 1.5.

Read more in PSD1059.

Action updates 2016-09-29

Action Group, version 1.6
– Bug Fix – Fixed a bug when using a Run Policy in the Action Group.

Add Session Objects from XML, version 1.1
– Bug Fix – When the chosen element does not contain any value, an empty value will be added to the session attribute.

Auto Attribute Populator, version 2.3
– New Feature – When using the advanced settings for a data source other than the default, there might be multiple objects in the query data source that match the attribute value in the source data source. It is now possible to choose whether all those objects should be added to the group or only one of them.

Base 64 Encode/Decode Attribute Values, version 1.7
– Bug Fix – When decoding a value, the decoded value could be wrong depending on the java version. This is now fixed.

Certificate Handler, version 1.7
– Removed dependencies of the deprecated version of the action.

Compare Values, version 1.5
– New Feature – The action now has support for comparing values using ‘greater than or equal’ (>=) and ‘less than or equal’ (<=).

Compose and Generate User ID, version 1.8
– Bug Fix – The character mapping now supports mapping a single character to multiple characters.

– Improvement – It is now possible to place the suffix after the incremental value in the user ID.

Powershell, version 1.7
– Improvement – For non-configured powershell arguments, the action will no longer use the value NO_VALUE. Instead that argument and any subsequent arguments will be skipped.

Write to LDAP, version 3.6
– Bug Fix – When using ‘add’ values and adding only one empty value to a multivalue attribute, the value in the attribute where replaced instead of added.

Upgrade of Existing Installation

Important step! Verify current configuration with new version in test environment.

If earlier versions of AAM exists, a complete reinstall of the application is required. So before doing the upgrade, please make sure to have a full backup of current installation/configuration. And also verify, in test environment, that current configuration works well with the new version.

If for some reason, verification in a test environment is not possible, an installation on current machine can be done, BUT, the reservations below must be addressed. The recommended way is still to use a separate environment for test.

Reservations when running on the same machine as current installation/version:
– The port for the internal database must be changed, adding the parameter DBPortNr=3105 in config.aam. Make sure to change the port number to something other than current port number.
– During installation, please make sure to unclick the installation of the service, because it will overwrite the current one.

Upgrade/Install of new version

Before uninstalling, make sure that you have a backup of current installation/configuration according to instructions above, where the most important files and folders are:

– <installPath>/AAM3/license/license.dat
– <installPath>/AAM3/config.aam and if they exist, all other *.aam files. Because of new functionality, older versions of *.aam files will be upgraded during the first usage and NOT be compatible with earlier versions!
– <installPath>/AAM3/db/
– <installPath>/AAM3/ext/ if 3rd party libraries has been used.

Now, initiate an uninstall of the application. After completion delete the folder <installPath>/AAM3 and remaining files if they exists.

After installation of the new version has completed, copy config.aam to <installPath>/Provisioning/.
Also, if any additional action packages, besides standard and extended actions, are used and not available as jar files, the database needs to be copied as well.

Additional guidance can be found in the installation guide.