Question Invalid parameters for LDAP in client config file?? how to solve this?

New to Plastic SCM, and some projects always popup these error, yet some wouldn't. i failed finding an answer or solution for this.

is it about client.conf? i don't see any unusual in it.....
and it is not the case the link below for adding a @cloud
Resolved - plastic scm: server spec is not correct - Unity Forum

 

del it and sign-in still shows the error. using Plastic SCM (CN) 1.2.2 and unity editor 2021.3.20f1c1, and switch to the non-Preview version Plastic SCM 1.0.0 and editor 2020.3.35f1c2 for testing got the same result.
is this some sort of nation related bug? anyway, the conf is all below:

<?xml version="1.0" encoding="utf-8"?>
<ClientConfigData xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<Language>zh-Hans</Language>
<WorkspaceServer>my_org@cloud.cn</WorkspaceServer>
<WorkingMode>SSOWorkingMode</WorkingMode>
<SecurityConfig>my_email_address</SecurityConfig>
<MergeTools>
<MergeToolData>
<FileExtensions>.doc;.docx</FileExtensions>
<Tools>
<string>"C:\Program Files\PlasticSCM5\client\diffscripts\merge-doc.exe" "@destinationfile" "@sourcefile" "@output"</string>
</Tools>
</MergeToolData>
<MergeToolData>
<FileExtensions>.prefab;.unity</FileExtensions>
<Tools>
<string>"C:\Program Files\Unity\Hub\Editor\2019.2.14f1\Editor\Data\Tools\UnityYAMLMerge.exe" merge -p "@basefile" "@sourcefile" "@destinationfile" "@output"</string>
<string>mergetool -b="@basefile" -bn="@basesymbolic" -bh="@basehash" -s="@sourcefile" -sn="@sourcesymbolic" -sh="@sourcehash" -d="@destinationfile" -dh="@destinationhash" -a -r="@output" -t="@filetype" -i="@comparationmethod" -e="@fileencoding" -m="@mergetype" -re="@resultencoding" --progress="@PROGRESS" --extrainfofile="@extrainfofile"</string>
</Tools>
</MergeToolData>
<MergeToolData>
<FileType>enTextFile</FileType>
<FileExtensions>.meta</FileExtensions>
<Tools>
<string>mergetool -b="@basefile" -bn="@basesymbolic" -bh="@basehash" -s="@sourcefile" -sn="@sourcesymbolic" -sh="@sourcehash" -d="@destinationfile" -dh="@destinationhash" -a -r="@output" -t="@filetype" -i="@comparationmethod" -e="@fileencoding" -m="@mergetype" -re="@resultencoding" --progress="@PROGRESS" --extrainfofile="@extrainfofile"</string>
</Tools>
</MergeToolData>
<MergeToolData>
<FileType>enTextFile</FileType>
<FileExtensions>*</FileExtensions>
<Tools>
<string>mergetool -b="@basefile" -bn="@basesymbolic" -bh="@basehash" -s="@sourcefile" -sn="@sourcesymbolic" -sh="@sourcehash" -d="@destinationfile" -dh="@destinationhash" -a -r="@output" -t="@filetype" -i="@comparationmethod" -e="@fileencoding" -m="@mergetype" -re="@resultencoding" --progress="@PROGRESS" --extrainfofile="@extrainfofile"</string>
</Tools>
</MergeToolData>
<MergeToolData>
<FileType>enBinaryFile</FileType>
<FileExtensions>*</FileExtensions>
<Tools>
<string>binmergetool -b="@basefile" -bn="@basesymbolic" -bh="@basehash" -s="@sourcefile" -sn="@sourcesymbolic" -sh="@sourcehash" -d="@destinationfile" -dh="@destinationhash" -a -r="@output" -m="@mergetype"</string>
</Tools>
</MergeToolData>
</MergeTools>
<DiffTools>
<DiffToolData>
<FileExtensions>.doc;.docx</FileExtensions>
<Tools>
<string>wscript.exe "C:\Program Files\PlasticSCM5\client\diffscripts\diff-doc.js" "@sourcefile" "@destinationfile" //E:javascript</string>
</Tools>
</DiffToolData>
<DiffToolData>
<FileExtensions>.xls;.xlsx</FileExtensions>
<Tools>
<string>wscript.exe "C:\Program Files\PlasticSCM5\client\diffscripts\diff-xls.js" "@sourcefile" "@destinationfile" //E:javascript</string>
</Tools>
</DiffToolData>
<DiffToolData>
<FileExtensions>.ppt;.pptx</FileExtensions>
<Tools>
<string>wscript.exe "C:\Program Files\PlasticSCM5\client\diffscripts\diff-ppt.js" "@sourcefile" "@destinationfile" //E:javascript</string>
</Tools>
</DiffToolData>
<DiffToolData>
<FileExtensions>.odt;.ods</FileExtensions>
<Tools>
<string>wscript.exe "C:\Program Files\PlasticSCM5\client\diffscripts\diff-odt.vbs" "@sourcefile" "@destinationfile" //E:vbscript</string>
</Tools>
</DiffToolData>
<DiffToolData>
<FileType>enTextFile</FileType>
<FileExtensions>*</FileExtensions>
<Tools>
<string>$internal_tool</string>
</Tools>
</DiffToolData>
<DiffToolData>
<FileType>enBinaryFile</FileType>
<FileExtensions>*</FileExtensions>
<Tools>
<string>binmergetool -s="@sourcefile" -sn="@sourcesymbolic" -d="@destinationfile" -dn="@destinationsymbolic" -a -t="@filetype" -i="@comparationmethod" -e="@fileencoding"</string>
</Tools>
</DiffToolData>
</DiffTools>
<ShowPerformanceWarnings>yes</ShowPerformanceWarnings>
<MergeWithPendingChanges>no</MergeWithPendingChanges>
<StackTrace>no</StackTrace>
<SetFilesAsReadOnly>no</SetFilesAsReadOnly>
<SetRevisionFileDate>no</SetRevisionFileDate>
<SupportSmbWorkspaces>no</SupportSmbWorkspaces>
<PerformAddPlusCi>no</PerformAddPlusCi>
<CheckFileContentForChanged>no</CheckFileContentForChanged>
<CaseSensitiveFsOnMac>no</CaseSensitiveFsOnMac>
<SameItemDifferentCaseError>no</SameItemDifferentCaseError>
<CheckinQueuesSize>50</CheckinQueuesSize>
<DownloadPoolSize>6</DownloadPoolSize>
<LastRunningEdition>cloud</LastRunningEdition>
</ClientConfigData>

 

after i removed the plastic scm cn-version and add unity version control package, errors gone .
so is version control the replacement of plastic scm?

still , the replies:
1.no, the project is fine , just not able to pull push etc.

2.in the profiles.conf :
<ServerProfile>
<Name>local_SSOWorkingMode_[4 number has changed after replacement of version control]<Name>

3.no .

 

yes , initially i didn't install the version control just using the hub to uploading project then automatically get installation of the plastic.
after this thread posted i searched the China developer forum , and got some useful thing like adding "com.unity.collab-proxy" to manifest , what installed proved to be version control package with version of 2.0.1 considering the latest.
thus , com.unity.collab-proxy is exactly the version control package? and it is a wrapper for plastic? correct me if i mistaken it