"The application's digital signature has an error. Do you want to run the application?
The digital signature was generated with a trusted certificate but has expired or is not yet valid"

"The security certificate has expired or is not yet valid."

Functionality and security are not affected. The warning message indicates the expiration of the signature originally provided in the security certificate used with certain Lotus QuickPlace applets. For additional background information, refer to "Security certificate expiration messages generated from Domino applets (May 18, 2009)" (#1381298).

The affected applet and associated JAR file for Lotus QuickPlace is

• PeopleOnline31.jar, used for awareness with Lotus Sametime

  typical path: C:\Domino\data\LotusQuickr\PeopleOnline31.jar

Resolving the problem

Steps are provided below to update the applet file to prevent your users from seeing this warning message. If you are not integrating Lotus Sametime with Lotus QuickPlace, then you are not using the affected applets and no specific action is required.

As an alternative to updating the files as outlined below, you can also instruct users to select "Always Trust" content from IBM, as the applets are still valid. The warning message is only to notify users that the certificate used to sign the applet has expired. The expiration does not affect an applet's security or functionality. In most cases, the user can click to "Always Trust" content from IBM to stop the message from appearing in the future.

To update Lotus QuickPlace with the re-signed applets to prevent the warning message from appearing to your users, take the following steps:

1. Update the Lotus QuickPlace JAR files

• Download the updated files for your version from from IBM Fix Central:
  
  QuickPlace 7.0 resigned applets
  
  QuickPlace 6.5.1 resigned applets
  
  
  You can also refer to "Download re-signed Java applets for Lotus QuickPlace" (#4023081) for direct links to the download and steps to apply.
  

  Note: Lotus QuickPlace 7.0 also uses a signed version of the STcomm.jar file from the Sametime SDK for integration. This 7.0 fix contains re-signed files for both PeopleOnline31.jar and STcomm.jar.

  The QuickPlace 6.5.1 Sametime setup uses an unsigned version of STcomm.jar, so is not impacted by this signature warning. Only the PeopleOnline31.jar file is re-signed and updated in the 6.5.1 fix.

2. Check for any additional Sametime actions

• Because you are using Sametime integration, review the steps to update your Lotus Sametime server version in "Sametime applets signer certificate expires on 18 May 2009" (#1380778).

• Apply the Domino fixes for your Lotus Domino server version as documented in "Security certificate expiration messages generated from Domino applets (May 18, 2009)" (#1381298). While not required for Lotus QuickPlace, it is a best practice to keep these Domino files up to date.

• After applying the latest applets, your users will be prompted to trust the new certificate used for signing the applets. This is normal. The first time a signed applet is installed, Web users are prompted. This prompt will be a one-time confirmation, which is not an indication of any problem.