What Do I Do If the ServiceCenter Login Page Cannot Be Accessed After ServiceCenter Is Mapped to the Public Network

9

【Product�?
ServiceCenter

【Version�?
3.0, 3.0.SPC2, 3.0.5, 3.0.5.SP1, 3.0.5.SP2, 3.0.5.SP3, 3.0.5.SP5, 3.0.7, and 3.0.8

【Fault Type�?
System fault

【Symptom�?
The ServiceCenter login page cannot be displayed after ServiceCenter is mapped to the public network.

【Fault Locating�?
Run the white-ls-cfg show command on the active and standby ServiceCenter nodes. The command output indicates that the whitelist is not configured. After the public network IP address is added to the whitelist, the ServiceCenter login page can be accessed.

【Root Cause�?
The public network IP address is not added to the ServiceCenter whitelist.

【Solution�?
Step 1 Log in to the active and standby ServiceCenter nodes as user galaxmanager.

Step 2 Run the white-ls-cfg show command on the active and standby ServiceCenter nodes and check whether the public network IP address is added to the whitelist.
If no IP address is displayed, the public network IP address is not added to the whitelist.

Step 3 If the public network IP address is not configured, run the following command on the active and standby nodes to add the public IP address to the whitelist:
white-ls-cfg add Public network IP address

----End

Other related questions:
What Do I Do If the Domain Name Cannot Be Used to Log In to ServiceCenter After ServiceCenter Is Mapped to the Public Network Because the Domain Name Is Not Added to the Whitelist
【Product�? ManageOne ServiceCenter 【Version�? 3.X 【Question�? What do I do if the domain name cannot be used to log in to ServiceCenter after ServiceCenter is mapped to the public network because the domain name is not added to the whitelist? 【Answer�? Step 1 Log in to the ServiceCenter active and standby nodes as user galaxmanager. Step 2 Run the white-ls-cfg show command on the active and standby nodes to check whether the domain name is added to the whitelist. If no domain name is displayed in the command output, the domain name is not added to the whitelist. Step 3 Run the following command on the active and standby nodes to add the domain name to the whitelist: white-ls-cfg add Domain name ----End

What Do I Do If the Organization Administrator Cannot Log In to the ServiceCenter Administrator Portal After ServiceCenter Is Upgraded to 3.0.5 or Later
【Product�? ServiceCenter 【Version�? 3.0.5 【Fault Type�? System fault 【Symptom�? After ServiceCenter is upgraded to 3.0.5 or later, the organization administrator cannot log in to the ServiceCenter administrator portal. 【Fault Locating�? According to the release notes, ServiceCenter 3.0.5 or later version does not allow the organization administrator to log in to the ServiceCenter administrator portal. 【Root Cause�? In ServiceCenter 3.0.5 or later version, the organization administrator can only log in to the ServiceCenter tenant portal. For details, see the ServiceCenter 3.0.5 release notes. 【Solution�? None ----End

What Do I Do If a License Cannot Be Imported to ServiceCenter Because It Contains Invalid Characters
【Product�? ServiceCenter 【Version�? 3.0, 3.0.SPC2, 3.0.5, 3.0.5.SP1, 3.0.5.SP2, 3.0.5.SP3, 3.0.5.SP5, and 3.0.7 【Fault Type�? License fault 【Symptom�? When a license is imported to ServiceCenter, the error message "The request has Invalid parameter: <, >." or "The request has invalid parameter <, >" is displayed. 【Fault Locating�? The error message displayed on the page indicates that the license contains special characters such as angle brackets <>. Special characters will result in a verification failure. 【Root Cause�? The license file contains angle brackets <>. After the license is imported to ServiceCenter, the security framework verifies the license file. The verification will fail to prevent XSS attacks if special characters are found. Check the BOQ and find that the site information contains angle brackets <>. The license file generated on the ESDP platform contains the site information. As a result, the license contains special characters. 【Solution�? Temporary Solution After an ESN change (set ESN Change Type to Without revocation code) is performed on the ESDP platform, the changed ESN is still the original ESN. After the change, the new license file does not contain angle brackets <>. Final Solution This problem will be resolved in ServiceCenter 3.0.8. ----End

If you have more questions, you can seek help from following ways:
To iKnow To Live Chat
Scroll to top