In a basic configuration, logging is done to the application server logs.

Listing 1. Log location for password application in Windows

C:\Program Files\Ubisecure\ubilogin-sso\tomcat\logs\xxxxx-stderr.YYYYMMDD.log
C:\Program Files\Ubisecure\ubilogin-sso\tomcat\logs\xxxxx-stdout.YYYYMMDD.log
C:\Program Files\Ubisecure\ubilogin-sso\tomcat\logs\xxxxx.YYYY-MM-DD.log

Listing 2. Log location for password application in Linux

/usr/local/Ubisecure/ubilogin-sso/tomcat/logs/xxxxx-stderr.YYYYMMDD.log
/usr/local/Ubisecure/ubilogin-sso/tomcat/logs/xxxxx-stdout.YYYYMMDD.log
/usr/local/Ubisecure/ubilogin-sso/tomcat/logs/xxxxx.YYYY-MM-DD.log

Successful startup is indicated with the following entry

INFO: Ubilogin Password started

Successful shutdown is indicated with the following entry

INFO: Ubilogin Password stopped

Enable debug level logging in problem cases, add to ubilogin-sso/ubilogin/webapps/password/WEB-INF/web.xml:

<context-param>
    <param-name>log-level</param-name>
	<param-value>debug</param-value>
</context-param>

Security consideration

LDAPS should always be used for the connection to the user repositiory where a password reset is done.

See Configuring the connection for basic LDAP integration - SSO for LDAP connection configuration.

Browser not supported