Tuesday, April 15, 2014

Version file not updated after OpenAM is patched

I am preparing myself for an engagement in a customer's site tomorrow to patch their OpenAM deployment from 10.0.0 to 10.0.2.

I blogged about OpenAM version 10.0.2 before. You can read it here - OpenAM 10.0.2 released!

The upgrade process is fairly easy. But of course, remember to backup, backup, and backup! You never know what will happen.

Clicking on "Save Report" will download a OpenAM Upgrade Report on the activities that the upgrade is going to take.

OpenAM Upgrade Report
Created: 20140415144314
Existing Version: OpenAM 10.0.0 (2012-April-13 10:24)
New Version: OpenAM 10.0.2 (2013-December-12 18:38)

Services Upgrade Report
New Services
* None
Modified Services
* sunAMAuthADService
Added attribute openam-auth-ldap-operation-timeout
Added attribute openam-auth-ldap-heartbeat-interval
Added attribute openam-auth-ldap-heartbeat-timeunit
Removed attribute iplanet-am-auth-ldap-server-check

New Sub Schemas
* None
Deleted Services
* None

Server Default Upgrade Report
New Attributes
* attr name: com.sun.identity.authentication.multiple.tabs.used : value: false

Modified Properties
* attr name: com.iplanet.am.version
old value: OpenAM 10.0.0 (2012-April-13 10:24)
new value: OpenAM 10.0.2 (2013-December-12 18:38)

Deleted Properties
* attr name: com.sun.identity.authentication.mutiple.tabs.used

Based on the Upgrade Report above, the embedded OpenDJ which is used as the default configuration store will update a value in the LDAP attribute called "com.iplanet.am.version".

I found there is a .version text file in the file system.

Before the upgrade, the content within the .version was: OpenAM 10.0.0 (2012-April-13 10:24)

After the upgrade, nothing was changed. But everything runs fine.

Strange indeed.


1 comment:

  1. This is https://bugster.forgerock.org/jira/browse/OPENAM-3270 . Only ssoadm uses it, nothing to be afraid of.