Resolve issue where the Single Sign On fails when Browser language set to fr or fr-CA in EngageOne 4.x

EngageOne 4.2, 4.3.

Product Feature: Installation


When using Single Sign On, users who have their browser locale language set to de, es, fr, or fr-CA are unable to log into EngageOne. They are instead prompted with a Windows Security login box, which never allows the user to get into the app.

If a user has successfully logged on to the system with their language set to English at least once, they will be able to get in by using the full app link (/viewpoint-client/apps/interactive/#/home) followed by a page refresh.

Attempting to hit the base URL (/viewpoint-client) on a French browser does not seem to work regardless of whether or not the user has logged in successfully previously.


The EngageOne 4.2 and 4.3.0 installation did not include the WindowsDesktopSSO.xml files needed by OpenAM for the locales de, es, fr, and fr-CA.

This leads to an incorrectly formatted http header to be sent as part of the SSO redirect, and a subsequent failure to pass on the Kerberos token needed for the authentication.


UPDATED: October 31, 2017
For EngageOne versions 4.2, 4.2.1, and 4.3.0, the following workaround can be used:

1. Edit the 'WindowsDesktopSSO.xml' file for the corresponding locale.
This file is found under the path like this (example for French Canadian):

Edit that file and change the existing value of the <HttpHeader> element to "Authorization".
For example, for the French Canadian locale, edit the file to change

2. Restart the EngageOne components, ensuring that the OpenAM restart has completed before the others.

3. Delete the browser caches of any clients which had been used to connect to this EngageOne before the fix.

EngageOne 4.3.2 and later will include these changes out of the box.