2. An update on eBuy and eService Request browser compatibility issues
On October 1st 2015, a simplified authentication architecture with a new generic URL is available:
As mentioned above, this compatibility to Chrome and Firefox are addressed in October.
Since POODLE vulnerability (October 2014), Google and Mozilla are gradually increasing the security of their browsers by preventing the use of SSLv3, TLS 1.0 and TLS 1.1 protocols.Unfortunately, some parts of our IT Infrastructure can’t be upgraded fast enough and are no longer compatible with the newest browser versions.
The Business Portal is impacted; the user profile management sections (‘change preferences’ and ‘my profile’ menu at the top of the page) in the Business Portal are impacted => its authentication infrastructure is not compatible; the application infrastructure itself is compatible.
e-Buy is impacted => its infrastructure is not compatible.
eService Request is impacted => its authentication infrastructure is not compatible.
The following browsers are no longer compatible with the applications listed above:
Firefox V37 and higher
Our applications continue to work with Internet Explorer, Safari and Opera.
For Chrome V45:
If possible, do not install the latest version and keep version 44. The workaround exists and consists in launching Chrome application with additional security parameters. This is possible via a customized Chrome shortcut. For this reason, we strongly recommend not to edit your existing Chrome shortcut but creating a new customized one that you will use only for accessing the Business Portal.
1. Go to your computer desktop
2. Copy-paste your Chrome shortcut (or if it doesn’t exist, create one)
3. Right click and select ‘Properties’
4. Select the tab ‘Shortcut’
5. Modify the field ‘Target’ value into "C:\Program Files (x86)\Google\Chrome\Application\chrome.exe" --ssl-version-fallback-min=tls1
6. Optional: Go to the tab ‘General’ and in the top field edit the name ‘Google Chrome’ into a name that relates to ALE Business Portal; for example ‘Google Chrome for ALE Business Portal’
7. Click ‘OK’
8. Restart Chrome by using this new shortcut
9. You should be able to log in and access our application
After implementing this workaround, you are able to browse on Chrome again.
A workaround exists which is to change the “security.tls.version.fallback-limit” setting.1. Open Firefox
2. In Location bar, type about:config and press ENTER3. The about:config "This might void your warranty!" warning page may appear. Click “I'll be careful, I promise!” to continue to the about:config page4. Search the configuration setting “security.tls.version.fallback-limit” (you can type “fallback-limit” in the search field)5. Double click on the “security.tls.version.fallback-limit” setting
6. Change the value to 1 (set to 3 by default)
7. Click ‘OK’
8. Restart Firefox
9. You should be able to log in and access our applicationAfter implementing this workaround, you will be ready to browse on Firefox again.