Username case sensitivity issue during EIA v9 third parties certification

No networking involved

Connect to third parties webservice for third parties authentication, authentication prompt indicates user does not exist

Through investigation by third parties systems, it was found that the username submitted by EIA was uniformly converted to lowercase, thus the user could not be found in third parties systems, prompting a message that the username does not exist.

In the EIA pxc database table tbl_parameter, modify the value of the IF_CONTROL_LOWNAME_OR_ORINAME parameter to 0, indicating that case conversion will not be performed when authenticating with third parties, and the original username will be passed.

1. Find the pxc database address and execute the following command on any node system

kubectl get pod -A -owide | grep eiapxc-n1

Locate the pod address in the echo, usually starting with 177, such as 177.177.x.x

2. Use the address obtained in step 1 to log in to pxc with the following command

mysql -uroot -pDB-pwd@123 -h177.177.x.x

3. After entering pxc, switchover to the EAD database with the following command

use EAD;

4. As shown in the screenshot below, execute the command highlighted in the red box

5. Return to the foreground page of EIA, navigate to Automation - User Business - Business Parameters - Access Parameters, switch to the System Configuration Manual Activation tab, and click the Activate Now button.

6. Re-authenticate to proceed.