...
When Log Viewer is invoked, it initially loads the current Audit log file, selects the last page and scrolls directly to the bottom of the page, displaying the log entries that were last written by Ubisecure SSO.
Figure 1: Log Viewer initial view, viewing Audit log |
Note that initially the extended log entry information is not shown on the page, in order to make the event history more legible.
...
Logfile navigation buttons
These buttons navigate between the entire range of log files of the currently selected type – for example, seeing the same log type from the next or previous day.
...
Entry representation of Audit-Events:
About the different entry types (authentication method list, authentication method selection, login, etc.) and content of them see also Audit log description.
The "login" event (successful authentication)
Headers | Name by specification |
---|---|
REMOTE_ADDR | addr |
ACTION | "login" |
USER INFO |
INFO |
MASTER SESSION | masterSessionId |
LOGIN INFO | authMethod |
APPLICATION | application |
USER AGENT | userAgent |
The "invalid login" event
Headers | Name by specification |
---|---|
REMOTE_ADDR | addr |
ACTION | "invalid.login" |
USER INFO | loginName |
INFO | reason |
MASTER SESSION | masterSessionId |
LOGIN INFO | authMethod |
APPLICATION | application |
USER AGENT | userAgent |
The "ticket granted" event
Headers | Name by specification |
---|---|
REMOTE_ADDR | addr |
ACTION | "ticket granted" |
USER INFO | mappedUsername (userName) |
INFO | application URL |
MASTER SESSION | masterSessionId |
LOGIN INFO | requestId |
APPLICATION | application |
USER AGENT | userAgent |
The "access denied" event
Headers | Name by specification |
---|---|
REMOTE_ADDR | addr |
ACTION | "access denied" |
USER INFO |
INFO | reason |
MASTER SESSION | masterSessionId |
LOGIN INFO |
APPLICATION | application |
USER AGENT | userAgent |
The "logout" event
Headers | Name by specification |
---|---|
REMOTE_ADDR | addr |
ACTION | "logout" |
USER INFO |
INFO |
MASTER SESSION | masterSessionId |
LOGIN INFO |
APPLICATION |
USER AGENT | userAgent |
The "authentication method list" event
Headers | Name by specification |
---|---|
REMOTE_ADDR | addr |
ACTION | "authentication method list" |
USER INFO |
INFO |
MASTER SESSION | masterSessionId |
LOGIN INFO |
APPLICATION | application |
USER AGENT | userAgent |
The "authentication method selected" event
Headers | Name by specification |
---|---|
REMOTE_ADDR | addr |
ACTION | "authentication method selected" |
USER INFO |
INFO |
MASTER SESSION | masterSessionId |
LOGIN INFO | authMethod |
APPLICATION | application |
USER AGENT | userAgent |
The "assertion received" event
Headers | Name by specification |
---|---|
REMOTE_ADDR | addr |
ACTION | "assertion received" |
USER INFO |
INFO | authenticatorId / attributes |
MASTER SESSION | masterSessionId |
LOGIN INFO | authMethod |
APPLICATION |
USER AGENT | userAgent |
Entry representation of Diag-Events:
Diagnostics events all follow the same conventionAbout the different entry types (authentication method list, authentication method selection, login, etc.) and content of them see also Diag log description.
All events
Headers | Description |
---|
CONTEXT | Which |
web application caused the event ( | |
TYPE | Diagnostic entry type or the class name printing the event |
LEVEL | The log level |
IP ADDRESS | The client's ip address |
REQUEST ID
- |
MESSAGE |
The actual log message, in case of |