Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »

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{color:#ff0000}xxxxx-stderr.YYYYMMDD.log
C:\Program Files\Ubisecure\ubilogin-sso\tomcat\logs{color:#ff0000}xxxxx-stdout.YYYYMMDD.log
C:\Program Files\Ubisecure\ubilogin-sso\tomcat\logs{color:#ff0000}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>


Unsecure Connection

Please note, that information exchanged with LDAP is transmitted by a protocol susceptible to security breaches. It is strongly advised to implement SSL encryption in the LDAP protocol when accessing confidential information.

SeeĀ Basic LDAP Integration - Configuring the Connection for LDAP connection configuration.

  • No labels