SSO FAQs

This document introduces some common errors and solutions for single sign-on (SSO).

Problem:

After opening the console which displays that SSO is successful in IE, you are still prompted to log in when accessing the decision-making platform.

Cause:

Different from other browsers, IE has an extremely high level privacy, which causes the cookie returned by the platform to be unwritten after IE sends the SSO request.

Solution:

Lower the IE privacy level.

Problem:

SSO is not working because the user password contains special characters, such as hgyusdre+CVsdej+HU09Y6y==. But you can successfully log in using the password on the login page.

Cause:

You fail to directly access the platform through the SSO interface if the password contains special characters, so the password needs to be encoded.

Solution:

1. Open the browser console. Take Chrome as an example. Enter encodeURIComponent("password") on the console tab page to encode the password. 

2. Access the platform with the encoded password through the SSO interface.

Problem:

You fail to log in through SSO in IE, but after you enable the IE debug mode, login through SSO is successful.

Cause:

In SSO code, console.log() is used to print debugging information. In IE, however, this code is not executed by default and only takes effect when the debugging tool is enabled through the F12 key.

Solution:

Just mask the code for printing logs. Then you can log in normally. 

Problem:

SSO is unsuccessful in the intranet environment.

Cause:

SSO code with JS files referenced does not work in the intranet environment. 

Solution:

Download the JS files to your local device and modify the corresponding path. Take Ajax cross-domain asynchronous SSO as an example.

1. Download the corresponding copy of jQuery files from the Downloading jQuery page.

2. Place the downloaded jquery.min JS file in the webroot folder in the %FR_HOME%\webapps path.

3. Modify the path of the jquery.min JS file in the HTML file.

Problem:

During backend login, after switching users, you need to click the login button twice for the new user to log in.

Cause:

You can refer to the platform timeout period as the expiration time of backend login. Manual logout is required for frequent switching.

Solution:

When triggering the login interface, first trigger a logout, https://IP address:Port number/webroot/decision/logout/cross/domain, then access the backend login interface to enable the new user to log in.

Problem:

FR SSO sometimes fails for Weaver E9 on PC terminal, and an error is shown on the console tab page, displaying "Cannot read property 'loginId' of underfined."

Cause:

Normally, when you log in to the Weaver, Frlogin.js is triggered to obtain the login username. The problem is caused when you log in to the Weaver without the execution of the corresponding method to obtain the username.

Solution:

Delay the execution of the loginFR() method by modifying 100 to 1000. 

Solution:

Method 1: Change the value of the field starting with LoginVerificationConfig from true to false in the fine_conf_entity table in finedb, and restart the system.

Method 2: Access http://IP address:Port number/webroot/decision/login/cross/domain?fine_username=admin_username&fine_password=admin_password&validity=-1 to log in through the SSO interface, bypassing the authentication. After successful login, access webroot/decision.

Problem:

SSO is unsuccessful with right username and password entered. 

Cause:

The password contains special characters like # @ + - =.

Solution:

Modify the code of login.js by encoding the username and password through the encodeURIComponent method.

Problem:

Entering the password directly in the URL leads to a 400 error.

Cause:

The password contains special characters. Accessing the platform directly through the URL with unencoded password results in login failures.

Solution:

Encode the password and access the platform through the URL with the encoded password.