Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

In a basic configuration, logging is done to the application server logs.log events are printed to the SSO diagnostics log. Filter the log events with password web application name.


Successful startup is indicated with the following entries:

...

Code Block
languagetext
titleListing 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
Code Block
languagetext
titleListing 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
2022-09-19 10:15:10,464 password init INFO Ubilogin Password 9.1.00 starting 
... 
2022-09-19 10:15:10,977 password init INFO Ubilogin Password 9.1.0 started 


Successful shutdown is indicated with the following entry:

Code Block
languagetext
INFO: 2022-09-19 10:15:10,977 password init INFO Ubilogin Password started

...

9.1.0 stopped

Sample warning:


Code Block
languagetext

...

INFO: Ubilogin Password stopped

...

2022-10-04 16:15:31,775 password com.ubisecure.ubilogin.password.change.ChangeServlet WARN CredentialsChange.change INVALID: VALIDATE: com.ubisecure.ubilogin.directory.spi.StatusException: INVALID: VALIDATE



Control the log levels by the application itself with the package name com.ubisecure.ubilogin.password in the logger configuration file.For more information, see SSO diagnostics log, Configuration.

For the package or class names by the libraries used contact IDS support.

Example debug configuration in include-logback.xml:


Code Block
languagetext

...

  <!--

...

 (10) Customise log levels 

...

-

...

Security consideration

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

...

->
  <logger name="com.ubisecure.ubilogin.password" level="DEBUG" />
  <logger name="com.ubisecure.saml2.metadata.URLMetadataLocator" level="DEBUG" />