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 kind of entries:
Code Block | ||
---|---|---|
| ||
2022-0910-1906 1012:1516:1021,464375 password init INFO Ubilogin Password 9.1.000 starting ... 2022-0910-1906 1012:1516:1023,977397 password init INFO Ubilogin Password 9.1.0 started |
Successful shutdown is indicated with the following kind of entry:
Code Block | ||
---|---|---|
| ||
2022-0910-1906 1012:15:1042,977822 password init INFO Ubilogin Password 9.1.0 stopped |
Sample warning:
Code Block | ||
---|---|---|
| ||
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 in use contact IDS support.
Example debug configuration in include-logback.xml
:
Code Block | ||
---|---|---|
| ||
<!-- (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.