Monitoring WSO2 IS Using WSO2 Analytics

This section explains how a Single Sign On (SSO) can be analyzed via WSO2 IS Analytics.

Prerequisites

The following prerequisites should be completed in order to try out this scenario.

• Configure a service provider for which statistics can be generated by following the instructions in Configuring Single Sign-On.

• Enable Analytics by Setting up Analytics in WSO2 IS.

  For this scenario, you need the following two listener configurations in the <IS_HOME>/repository/conf/identity/identity.xml file.

  <EventListener type="org.wso2.carbon.identity.core.handler.AbstractIdentityMessageHandler"
  name="org.wso2.carbon.identity.data.publisher.application.authentication.impl.DASSessionDataPublisherImpl"
  orderId="11" enable="true"/>

  <EventListener type="org.wso2.carbon.identity.core.handler.AbstractIdentityMessageHandler"
  name="org.wso2.carbon.identity.data.publisher.application.authentication.impl.DASLoginDataPublisherImpl"
  orderId="10" enable="true"/>

Step 1: Generate statistics

This step involves repeatedly logging into the travelocity web application in the single sign-on scenario that you have configured. This generates statistics that can be viewed in the Analytics Dashboard. Follow the procedure below to generate statistics for both successful and failed login attempts.

1. Access the travelocity web application using the following URL.
   http://wso2is.local:8080/travelocity.com/home.jsp

2. Within a time interval of one hour, make login attempts as follows in the given order. 
   1. 20 successful attempts
   2. 10 failed attempts
   3. 20 successful attempts

Step 2: Analyze statistics

This step involves analyzing the statistics generated for your log in attempts via the Analytics Dashboard. 

1. Access the IS Analytics Management Console using the following URL, and log in using your credentials.
   URL: https://<IS_Analytics_HOST>:<IS_Analytics_PORT>/carbon/ 
2. In the Main menu, click Analytics Dashboard. Then log into the Analytics Dashboard by entering your credentials. This opens the Dashboards  page where the Security Analytics dashboard is displayed as follows.
    
3. Click View to open the dashboard. Then click Last Hour. The following is displayed.
   • The LOGIN ATTEMPTS OVER TIME gadget displays the total number of login attempts as 50.  The success rate is displayed as 80% and the failure rate is displayed as 20%. If you move the cursor to the area of the pie chart representing successful login attempts, a login attempt count of 40 is displayed as demonstrated below. Similarly, if you move the cursor to the area of the pie chart representing failed login attempts, a login attempt count of 10 is displayed.
      
   • The BY SERVICE PROVIDER gadget provides a comparison of the successful login count and the failed login count in a bar chart for the travelocity service provider used in this scenario. The successful/failed login count is displayed when you move the cursor over the relevant bar as demonstrated below. In this scenario, the number of successful login attempts is 40 and the number of failed login attempts is 10.
      
   • The BY USERSTORE gadget provides a comparison of the successful login count and the failed login count in a bar chart for the PRIMARY userstore used in this scenario. The successful/failed login count is displayed when you move the cursor over the relevant bar as demonstrated below. In this scenario, the number of successful login attempts is 40 and the number of failed login attempts is 10.
      
   • The BY ROLE gadget provides a comparison of the successful login count and the failed login count in a bar chart for each role assigned to the admin user of which the credentials were used to log into the travelocity web application. 
      
   • The BY USER gadget provides a comparison of the successful login count and the failed login count in a bar chart for the admin user of which the credentials were used to log into the travelocity web application. The successful/failed login count is displayed when you move the cursor over the relevant bar as demonstrated below. In this scenario, the number of successful login attempts is 40 and the number of failed login attempts is 10 for all three roles.
     
   • The DATA TABLE gadget provides detailed information about each individual log in attempt as shown below.