The log viewer will display events such as IdP self healing / granular access engine logs and other features of the Dashboard as they are developed.
At present only the granular access engine logs will be displayed in this log viewer.
The log viewer provides you with an easy to use, intuitive interface to browse the logs. In the top right hand corner is the date/time selector – clicking on this will allow you to specify a date range to display log entries across. You can set a custom start and end date, or use our handy pre-set date functions such as “This month” / “Last year” / “This year” etc. By default when the page loads it will be displaying data from this year.
The number of log entries displayed per page can be increased by adjusting the “Show ‘x’ entries” drop down menu on the top left hand corner of the screen. Or you can simply filter through the results by using the pagination links at the bottom of the log event table.
Underneath the date/time selector we have a search box which can be used to search over all the data contained in the log event table across all pages of the result data set. This allows us to search the results for a specific user ID / service provider / user group name etc. So it would be possible for us to see all instances where a user was denied access to a service provider/resource by typing “denied” into the search box.
Data can be sorted into ascending and descending order by clicking the arrow icons at the top of each column on the table.
The log viewer table currently displays the following data:-
- Date/time of the event
- Entity ID or friendly name of the service provider / resource
- The name of the granular access rule if one was found
- User ID
- The LDAP groups which that user belongs to
- The IdP node which the log was made on if the IdP is load balanced
- The outcome of the rule (whether the user was allowed or denied access to the resource)
You can use the data in the log viewer to track down issues that users may be experiencing when logging into resources or to check that the granular access rules you’ve created are working correctly.