IBM SCORE Support for Google Chrome

Resolving The Problem

Java Plugin Support (NPAPI)
Google announced that it will be phasing out NPAPI support for Chrome. This effectively means that Java will no longer be supported in Chrome. IBM SCORE requires Java running in the browser for the transfer of documents to client machines.
With Google Chrome version 42 NPAPI support has been disabled by default. Using this version, or later, IBM SCORE users will not be able to view, check-out, or check-in documents. IBM recommends that you use a supported version of Google Chrome or switch to a supported version of Microsoft Internet Explorer. Please refer to the Support software versions for IBM SCORE 6.1.1 page for supported browser version information:
http://www-01.ibm.com/support/docview.wss?uid=swg21358610

For further information on Google Chrome's support of NPAPI please refer to the following pages:

https://java.com/en/download/faq/chrome.xml
http://blog.chromium.org/2014/11/the-final-countdown-for-npapi.html
https://www.chromium.org/developers/npapi-deprecation

Chrome Auto Updates
Chrome is frequently updated with new major and minor fixes. By default it will always update when it detects new updates are available. These updates include security patches. Please consult the Chrome documentation to prevent Chrome from auto-updating. Users of Microsoft Windows Group Policy and Active Directory can check the following page for instructions on how to disable Google Update http://support.google.com/installer/bin/answer.py?hl=en&answer=146164

Chrome Configuration
Chrome can be configured in a number of ways by both system administrators and users. The Chrome documentation provides help on setting Group Policies and Active Directory settings. Instructions for these can be found here http://dev.chromium.org/administrators. There are some useful settings that can be set either by Group Policy administrators or by users.
Useful Administrator Settings

AllowOutdatedPlugins
When the browser attempts to use a plug-in and it detects that the plug-in is out of date, it will inform the user, interrupting the plug-in, and ask if the user wishes to run the plug-in this time or update it. Disabling this will stop Chrome from interrupting plug-ins every time they run it to request that the user updates. This can be disabled by using the following values with Group Policy http://dev.chromium.org/administrators/policy-list-3#AllowOutdatedPlugins

DisabledPlugins
Chrome is supplied with its own PDF Reader which will need to be disabled so that Adobe Reader or Adobe Acrobat plug-ins can be used. This can be disabled, along with other plug-ins, by using the following values with Group Policy http://dev.chromium.org/administrators/policy-list-3#DisabledPlugins

Useful Client Settings
If these settings will not be set through Group Policy then they can be set using alternate means.

AllowOutdatedPlugins
The user can enable this setting locally. Right click on the Google Chrome icon on the desktop. Under the Shortcut tab append “ --allow-outdated-plugins” without quotes to the end of the Target field. An example Target will look like this; "C:\Documents and Settings\User\Local Settings\Application Data\Google\Chrome\Application\chrome.exe" --allow-outdated-plugins. For more information please see http://support.google.com/chrome/bin/answer.py?hl=en&answer=1181003&topic=1678462&ctx=topic

DisabledPlugins
The user can enable this setting locally. Open Chrome and enter “chrome://plugins” into the address bar without quotes, then press enter. Locate the plug-in Chrome PDF Viewer and click the blue hyperlink Disable. This will disable Chrome PDF Viewer and allow Adobe Reader or Adobe Acrobat to be launched when viewing PDFs. For more information please see http://support.google.com/chrome/bin/answer.py?hl=en&answer=142056&topic=1678462&ctx=topic

Known Issues
Chrome keeps reporting that plug-ins are out of date for Java or Adobe.
Please see the topics on AllowOutdatedPlugins under Useful Client Settings or Useful Administrator Settings.

If these settings are enabled already check that this is picked up by Chrome by entering the following URL in the address bar “chrome://version”. There will be a list of information including the heading Command Line. Ensure that the outdated plugin command line option is displayed as expected:

Command Line "C:\Documents and Settings\Paul\Local Settings\Application Data\Google\Chrome\Application\chrome.exe" --allow-outdated-plugins --flag-switches-begin --flag-switches-end

Although AllowOutdatedPlugins is enabled, Chrome displays the Java Applet with an error about Java Plugin being out of date but provides no options to run or update the plugin.
Try updating the JRE on the system to be more up to date. Chrome seems to have trouble loading some older versions of Java even if the AllowOutdatedPlugins Command Line option is enabled. If there are still issues with this, contact Chrome Support.

PDF Files do not open in Adobe Acrobat or Reader
Please follow the topics on DisabledPlugins under Useful Client Settings or Useful Administrator Settings.

File transfers to the client leaves a blank window open
This window is opened to enable the transfer. In IE that window is closed if the user chooses to open the file, Chrome leaves the window open.

Reporting Issues
For issues with Chrome please check the documentation for Chrome http://support.google.com/chromeos/a/?hl=en.

For issues with IBM SCORE while using Google Chrome, please use the following Technote as guidance for information to collect http://www-01.ibm.com/support/docview.wss?uid=swg21245263

In addition please include the following information:
Browser Version
Open Chrome and enter “chrome://version” into the address bar without quotes, then press enter. Copy and Paste all information on that page to be provided in any support requests.

Plug-ins
Open Chrome and enter “chrome://plugins” into the address bar without quotes, then press enter. At the top of the browser page on the right hand side will be a ‘+’ symbol title “Details”. Click on the ‘+’ symbol to see extra information about plugins. Look for any plug-ins relevant to the problem and copy and paste the detailed information