Ubisecure CustomerID needs two web agents. The first one is used to provide login functionality to the Ubisecure CustomerID user interfaces and it also provides the LDAP user account that Ubisecure CustomerID uses when accessing Ubisecure Directory. The second web agent is used when performing verifications during registrations. Ubisecure CustomerID installation package contains LDIF import files that need to be imported to Ubisecure Directory using the import functionality of Ubisecure SSO.
Importing the web
...
agents:
This section assumes Ubisecure CustomerID is installed on a different server than Ubisecure SSO. See below if Ubisecure CustomerID is installed on the same
...
server as Ubisecure SSO
...
.Import
- Copy the LDIF files
...
- found from
%PROGRAMFILES%\Ubisecure\customerid\application\ldapon the Ubisecure CustomerID server to Ubisecure SSO server. You can place them on the desktop in a folder calledcustomerid-ldifs. Use the
import.cmdscript in the pathUBILOGIN_HOME\ldap\adam\import.cmdto import these filesCode Block language text cd /D "%PROGRAMFILES%\Ubisecure\
...
ubilogin-sso\
...
ubilogin\ldap\adam" import.cmd "%USERPROFILE%\Desktop\customerid-ldifs\customerid.ldif" import.cmd "%USERPROFILE%\Desktop\customerid-ldifs\customerid-secrets.ldif" import.cmd "%USERPROFILE%\Desktop\customerid-ldifs\customerid-adlds.ldif
...
Importing the web agent when CustomerID is on a separate host than SSO:
- Copy the relevant LDIF files from CustomerID server to SSO. You can place them on the desktop in a folder called "customerid-ldifs"
- Use the
import.cmdscript in the pathUBILOGIN_HOME\ldap\adam\import.cmdto import these files" - Securely remove the temporary files from the desktop.
| Info | |||||
|---|---|---|---|---|---|
If Ubisecure CustomerID is installed on the same server as Ubisecure SSO, this command can be run in place.
|
...
|
...
|
...
|