WebSphere Plugin Key & Password Expiration 4/26

Accelerated Value Announcement:  WAS Alert affecting ICS Products !

WebSphere Plugin Key & Password Expiration 4/26

Overview:    WAS Support posted two Flash Alerts to customers about Expirations on 4/26.  These expirations could have significant impact to production environments if not addressed. The following alert applies to all products that are built on top of WebSphere Application Server, for example: Portal, Sametime, Connections, and Quickr J.

ACTION:  Make sure that your customers are aware of these items and the April 26th date .

1)The password to the Plugin-key.kdb file  that is shipped with the WebSphere Plugin install will expire on April 26, 2012:
 
Please refer to the following link for additional details.  

http://www-01.ibm.com/support/docview.wss?uid=swg21588312

The impact  of the "password expiration issue in the above flash" is that the https transport between the WebSphere plugin and back-end AppServers will stop working, if not resolved.  It means that the Plugin-key.kdb (and the personal & signer certificates in it) will not be loaded during the plugin initialization and the https transport will not be used.

2) The personal certificate  called "WebSphere Plugin Key" within the plugin-key.kdb that is shipped with the WebSphere Plugin install will expire on April 26, 2012:

Please refer to the following link for additional details.  

http://www-01.ibm.com/support/docview.wss?uid=swg21577327

This will affect those WebSphere AppServers that are configured to require SSL client authentication (SSL mutual authentication) and that are using the default WebSphere plug-in key.  Most of our customers did not configure WebSphere AppServers to use SSL mutual authentication between the plug-in and WebSphere AppServers.

We CAN Move From SharePoint to IBM!

So I have not posted for a while, and for good reason.  I have been working almost exclusively with the same customer since November on a really cool project and it is finally reaching a point that I can talk about it… a bit.  We (Ascendant) partnered with IBM and T-Systems to bring to fruition a working content migration utility that can take content FROM SharePoint and populate it into Connections / Quickr / WCM.  (Yes… any or all of the three mentioned have a native connector for the utility from T-Systems now thanks to our project.)  Beyond just grabbing the content, transforming it, and then pushing it into the correct content area, we are able to maintain content ownership and impersonate other users at migration time without impacting those users.  This is truly a first of it’s kind solution to the best of my knowledge.  Hats off to the whole team we have been working with.  I know I am excited to be part of this, as I am sure most of the other team members are as well.  This brings real choice to the market as people now have the availability to move their content between platforms.

Thank You everyone that made this possible!

Sametime Applets to Expire

Sametime Meeting applets certificate expires March 19; updated applets available
The Sametime Meeting Server applets are signed with a certificate that expires on 19 March 2012.  If you administer a Sametime 8.0 server or a Sametime 8.5.0 environment that uses the Classic Meeting server, you should download and apply updated Sametime applets to prevent your users from seeing a warning about the expired certificate.  For more details and links to the updated applets, refer to "Sametime applets signer certificate expires on 19 March 2012" (#1580492)

QuickrD Bug

A while back, I was made aware of an issue where the Notes client will increase the size of fonts in emails when sent back and forth multiple times.  This link points to the problem description:

https://www-304.ibm.com/support/docview.wss?uid=swg21201323

The work around is to add a few variables to your servers notes.ini to address this.  So what does this have to do with Quickr?

I was recently discussing a Quickr 8.x > 8.5.1 upgrade when this was encountered.  If you have implemented the work around as listed in the above technote, it will break the Quickr login page.  The rendered HTML will be malformed, and you will not be able to use the Quickr login page which allows for non-directory members logging into the server / places.

Took a bit of figuring and a PMR, and I suspect this is a rare combination of circumstances, but if this can help anyone else, here it is.