Issue: When a user opens multiple SSO browser sessions for chromium-based browsers, this results in a conflict and sessions fail.
Workaround: For using the chromium-based browser as the SSO application, publish the batch file instead of publishing the browser path.
Sample batch files is as follows:
start chrome.exe --user-data-dir=%LOCALAPPDATA%\Google\Chrome\%SESSIONNAME% --load-extension="<absolute path of Secure login extension>" --start-maximized --new-window --app="https://my-application-url/" timeout 1 >nul
NOTE:In the app parameter, specify URL of the application to which users want to perform SSO.