What’s New in Automatic Account Manager 3.7

Facts

Product: Automatic Account Manager (AAM)
Platform: Any supported
Revision History

Version 3.7 released March 31st 2015

Read former release notes for AAM 3.3 here.
Read former release notes for AAM 3.4 here.
Read former release notes for AAM (Provisioning Service) 3.5 here.
Release 3.6 was an internal version, never released.

What’s New

The new version of AAM includes a number of improvements and new features.

With this release the product will be renamed from Nordic Edge Automatic Account Manager to PhenixID Automatic Account Manager.
The Google Apps additional action package has been updated to reflect the changes made in the Provisioning API from Google.
NB! Current Google Apps Provisioning API will not be supported by Google after April 20th 2015.

Important notes when upgrading to 3.7 release

– JAVA has been upgraded to a newer version, and this can mean different behavior in some cases. So please make sure to test your current configuration before implementing in production environment.

– If the action “Powershell” is being used it needs to be upgraded to version 1.5. It can be found here:
https://download.phenixid.se/wp/support/psd/Powershell_Action-2015-10-22.jar

– If “Launch” action is being used, double quotes (“) needs to be replaced with single quotes (‘).

– With the new JAVA, SMTP behavior has been changed. Please see document:
http://support.phenixid.se/psd/psd1042-smtpand-java/

– New feature, “LDAP connection pooling” has been added to version 3.7. It’s disabled by default. Please make sure to read the solution document below, before implementing this feature.

Core updates 3.7 build 34192

Look and feel

– The product name is now PhenixID Automatic Account Manager.
– The AAMStudio design has been changed to match PhenixID corporate design standards.
– The AAM service name has been changed to PHXID_AAM3.
– The AAM service display name has been changed to PhenixID Automatic Account Manager.
– The AAM default installation folder has been changed to phxid/AAM3/.
– Generated documentation is now displayed matching PhenixID corporate design standards.

LDAP connection pooling

New connection pool handling for LDAP directories.
Configure a connection to be reused for subsequent connections to the LDAP directory.
This will decrease the amount of connections being used.

Core updates 3.7 build 34451

Bug fixes

– Fixed a bug where an imported policy from an AAM version before policy specific logging could not be saved.
– Fixed a bug when updating LDAP attributes with an empty value, using the action Write to LDAP.

Action updates 2015-03-30

Write to LDAP by Delete and Add, version 1.0
– New action
– Performs replace of LDAP object by first deleting the current object, then adding the new object.

LDAP Connection Pool, version 1.0
– New action
– Performs operation on LDAP common connection pool.

Action updates 2015-04-29

Compare Values, version 1.4
– Bug Fix – Removed a null pointer exception when using an attribute with a value in a wrong format.

MultiValue Diff, version 1.5
– Improvement – A non-existing comparision attribute will be handled as an empty comparision attribute.

String Padding, version 1.1
– New feature – A new option to insert the characters at the end of the value instead of at the beginning.

Write to File, version 1.9
– New feature – It is now possible to insert a line break in the text.

Action updates 2015-09-15

MultiValue Diff, version 1.6
– Bug Fix – If the result is empty the result attribute will have an empty value instead of no value.

Split CSV, version 1.0
– New action – Split a comma separated value into multiple new attributes.

String Substring, version 1.1
– Bug Fix – The value will now be correct when handling more than one object.

Remove Values in Multivalue, version 1.5
– Bug Fix – The separator for multiple values is now changed back to semi-colon from comma.

Write to LDAP, version 3.6
– Improvement – No connection will be opened to the LDAP if no attributes need to be updated

Action updates 2015-10-29

Action Group, version 1.5
– Bug Fix – If a Session Object is added or removed within the action group, that will be reflected after the group as well as within the group.

Additional Action Packages

There is a number of additional action packages and step-by-step guides published at the AAM landing page.

Read more about the additional action packages updated with this release:

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/

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>/AAM3/.
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.
Read more in the installation guide.