...
Define UBILOGIN_HOME environment variable for the Ubisecure SSO server so that it points to the Ubisecure SSO installation path:
%PROGRAMFILES%\Ubisecure\ubilogin-sso\ubilogin
Code Block set UBILOGIN_HOME=%PROGRAMFILES%\Ubisecure\ubilogin-sso\ubilogin
- Copy the
cid-sso-adapter-package-x.x.x-windows.zip
file to the Ubisecure SSO server and extract it under the following folder:%PROGRAMFILES%\Ubisecure
Run the Ubisecure CustomerID SSO Adapter installation script:
Code Block language text cd /D "%PROGRAMFILES%\Ubisecure\cid-sso-adapter" install.cmd
There are now two new configuration files in the following folder:
%PROGRAMFILES%\Ubisecure\ubilogin-sso\ubilogin\webapps\uas\WEB-INF\
The new configuration files are:
attribute-prefix.index
eidm2-authorizer.properties
Also some new library files have now been added to the
%PROGRAMFILES%\Ubisecure\ubilogin-sso\ubilogin\webapps\uas\WEB-INF\lib
folder.You may now need to make some changes to the
eidm2-authorizer.properties
according to your installation configuration. Generally no changes are required. For more details, refer to the document Configuration - CustomerID.Run
update.cmd
on Ubisecure SSO in using the following command:Code Block language text "%PROGRAMFILES%\Ubisecure\ubilogin-sso\ubilogin\config\tomcat\update.cmd"
Ensure that the diagnostics SSO diagnostic log (
uas3sso_diag.yyyy-mm-dd.log
, which is by default located at%PROGRAMFILES%\Ubisecure\ubilogin-sso\ubilogin\logs
) contains the following rows (with the current time):Code Block language text 20162022-0910-0206 1307:5725:4925,021711 uas init INFO CustomerID Authorizer started 20162022-0910-0206 1307:5725:4925,021711 uas authz INFO eidm.authorizer: CidAuthorizer init started. 20162022-0910-0206 1307:5725:4926,209083 uas init INFO CustomerID SQL: customeriddb PostgreSQL x12.x.x8 20162022-0910-0206 1307:5725:4926,224130 uas authz INFO eidm.authorizer: CidAuthorizer init done. 20162022-0910-0206 1307:5725:4926,224130 uas init INFO eidm: com.ubisecure.customerid.authorizer.CidAuthorizer: started