Installation Process

In this chapter, the overall installation process is described. The Ubisecure SSO configuration is described in more detail in Configuration - SSO pages.

Model: Overview of the installation process.

Windows

Installation process steps in windows

Linux

Installation process steps in linux 

Verify that Ubisecure SSO Is Installed or Upgraded Successfully:

1. Review the ubilogin/logs/uas3_diag.YYYY-MM-DD.log  file.
   1. Confirm that no unexpected errors occurred since the previous restart.

   2. Confirm that the following entry exists:

      YYYY-MM-DD 15:33:24,080 init Ubilogin Authentication Server X.X.X_XXXXX started
      YYYY-MM-DD 15:33:24,184 tech ping: the system is alive

2. Access the Ubisecure Management application using the base url defined in uas.url in win32.config or unix.config file.

   https://sso.example.com:8443/ubilogin/

   You will be prompted to log in.
   The default administrator username is system and the password is admin.
   
   

   If system.password in file win32.config/unix.config has no value, a random password is generated and written to win32.config/unix.config.

   If system.password in file win32.config/unix.config has a non-default value, this password is used after upgrade.

   Figure 1. Login process

3. The next step is to change the password. This will be prompted automatically.

   Figure 2. Password change process

   
   

4. A successful new installation will look like this after log-in:

   Figure 3. Ubisecure Management after log-in

   The version number printed at the bottom of the Ubisecure Management console application is for the Ubisecure Management application only. The first two numbers here (e.g., 8.2) should match the installed version.

Note about update and server.xml/win32.config file changes

if some configuration is changed in the Win32.config -file, or in \ubilogin-sso\tomcat\conf\server.xml -file manually, the change doesn't take into effect if there is a server.xml in place in \ubilogin-sso\ubilogin\custom\tomcat -folder. This server.xml needs to be removed manually first, and then a new one is created with the changes

Continue installation By creating configurations in Configuration and setup application to create configurations