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

« Previous Version 3 Next »

Diagnostic log

In a basic configuration, 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:

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:

 2022-09-19 10:15:10,977 password init INFO Ubilogin Password 9.1.0 stopped

Sample warning:

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:


  <!-- (10) Customise log levels -->
  <logger name="com.ubisecure.ubilogin.password" level="DEBUG" />
  <logger name="com.ubisecure.saml2.metadata.URLMetadataLocator" level="DEBUG" /> 

Audit log

In a basic configuration, Password application audit log events are printed to this file: password_audit.YYYY-MM-DD.log in the ubilogin/logs folder.


  • No labels