Location via proxy:   [ UP ]  
[Report a bug]   [Manage cookies]                
SlideShare a Scribd company logo
Pandora FMS
Administrator Manual
Outlook Web Access Plugin
Administrator Manual Outlook Web Access
© Artica Soluciones Tecnológicas 2005-2012
Index
1Changelog...........................................................................................................................................3
2Introduction........................................................................................................................................4
2.1.How plugin works......................................................................................................................4
3Compatibility Matrix..........................................................................................................................5
4Documentation provided by the requesting area................................................................................6
5Modules provided by the plugin.........................................................................................................7
6Requirements......................................................................................................................................8
7Installing.............................................................................................................................................9
8Monitoring Configuration................................................................................................................10
8.1.Plugin Parameters ...................................................................................................................10
8.2.users.txt File Format ...............................................................................................................10
8.3.Creating a Plugin module ........................................................................................................11
1 CHANGELOG
Date Author Change Version
15/02/12 Dario First version v1r1
25/09/12 Dario Fixed bug in code v1r2
Page 3
2 INTRODUCTION
This document has as main objective the description of the Web Access Outlook monitoring plugin.
The purpose of the plugin is to monitor the correct work of the Outlook Web Access application.
2.1. How plugin works
The plugin checks that the OWA application is available for the user and that is possible to have
access to it using the user credentials.
The plugin does the same actions that an user will do with a web browser when using the service,
simulates a web navigation by the application asking for the main page and filling in and sending
the login form.
Besides this check, it allows to check the existence of specific errors that have taken place while
using this application.
For any of the checks, the plugin will return 1 or 0 depending on the check result, for example, if it
is imposible to log in, then the plugin will return 0. Another example could be if when doing the
check it finds the error string specified. In this case it will return 1, and if it doesn't find the string it
will return 0.
3 COMPATIBILITY MATRIX
The plugin compatibility matrix is the following:
Page 4
Systems where it has been tested
• SUSE Linux Enterprise Server 11
(x86_64)
• Outlook Web Access 14.355.2
Systems where it should work
• SUSE Linux Enterprise Server 11
(x86_64) or higher
• Outlook Web Access 14.355.2 or higher
It is posible that, due to changes in the login process, some changes in the plugin would be
necessary in the Outlook Web Acess.
4 DOCUMENTATION PROVIDED BY THE REQUESTING AREA
The requesting area must send the following information:
• Domain in which Outlook Web Access is installed.
Page 5
• Data from 5 users to perform the monitoring:
◦ User domain
◦ Username
◦ Password
• If an error detection is required the area must provide a list with the errors to monitor.
5 MODULES PROVIDED BY THE PLUGIN
The plugin can perform three kind of checks: login test, index test and error checking.
• The index test checks if the services is accessible loading the index page.
• The login test checks whether or not is possible to login into the application.
• The error tests could be used together with index and login checks and look for the error
Page 6
passed during the index and login tests.
6 REQUIREMENTS
For the correct work of the plugin, this software should be installed:
• Pandora FMS 3.2.1 Server or higher
• Perl Libraries:
Page 7
◦ libio-socket-ssl-perl
◦ libnet-ssleay-perl
Page 8
7 INSTALLING
To install the plugin, you will only have to copy it in a folder of the server, and after this register it
as a plugin in the plugin management Pandora Console section.
The configuration of the plugin register will be like this:
Page 9
8 MONITORING CONFIGURATION
8.1. Plugin Parameters
The plugin configuration parameters are the following:
• check_owa.sh --domain <domain> --check <check_type> --users_file <users_file> [--
error_str <error_string>]
• domain: Domain where the OWA server is installed.
• check: Check type, that could be:
◦ index: checks that it is possible to have access to the OWA welcome form.
◦ login: checks tht login using several users.
• user_file: file that contains the user credentials to test the login.
• error_str: (optional) checks if an specific error string is shown while navigation. It is
posible to use regular expressions.
An example that shows that it is checking the login is:
./check_owa.pl --domain "my.exchange.com" --check login --users_file users.txt
To check an error string we write:
./check_owa.pl --domain "my.exchange.com" --check login --users_file users.txt --error_str 403
8.2. users.txt File Format
This file has the credentials of the multiple users that are authorized to check that the login form
works correctly.
The file format is the following:
DOMAINuser1;password1
DOMAINuser2;password2
DOMAINuser3;password3
DOMAINuser4;password4
The best option is to use 5 users, because more makes the plugin execution slower.
The reason of using only 5 users is to avoid false positives if the accounts are blocked.
For this reason, checks will be always be done in base to the number of users of the
file.
Page 10
8.3. Creating a Plugin module
This plugin has to be registered in Pandora as server plugin.
When creating a module that uses this plugin it will be necessary to put all the parameters in the
Plug-in parameters field, for example:
P l u g - i n p a r a m e t e r s : - - d o m a i n m y d o m a i n . c o m – c h e c k l o g i n – u s e r s _ f i l e
/var/www/html/pandora_console/plugin/users2.txt –error_str 500
Page 11

More Related Content

Pandora FMS: Exchange OWA Plugin

  • 2. Administrator Manual Outlook Web Access © Artica Soluciones Tecnológicas 2005-2012 Index 1Changelog...........................................................................................................................................3 2Introduction........................................................................................................................................4 2.1.How plugin works......................................................................................................................4 3Compatibility Matrix..........................................................................................................................5 4Documentation provided by the requesting area................................................................................6 5Modules provided by the plugin.........................................................................................................7 6Requirements......................................................................................................................................8 7Installing.............................................................................................................................................9 8Monitoring Configuration................................................................................................................10 8.1.Plugin Parameters ...................................................................................................................10 8.2.users.txt File Format ...............................................................................................................10 8.3.Creating a Plugin module ........................................................................................................11
  • 3. 1 CHANGELOG Date Author Change Version 15/02/12 Dario First version v1r1 25/09/12 Dario Fixed bug in code v1r2 Page 3
  • 4. 2 INTRODUCTION This document has as main objective the description of the Web Access Outlook monitoring plugin. The purpose of the plugin is to monitor the correct work of the Outlook Web Access application. 2.1. How plugin works The plugin checks that the OWA application is available for the user and that is possible to have access to it using the user credentials. The plugin does the same actions that an user will do with a web browser when using the service, simulates a web navigation by the application asking for the main page and filling in and sending the login form. Besides this check, it allows to check the existence of specific errors that have taken place while using this application. For any of the checks, the plugin will return 1 or 0 depending on the check result, for example, if it is imposible to log in, then the plugin will return 0. Another example could be if when doing the check it finds the error string specified. In this case it will return 1, and if it doesn't find the string it will return 0. 3 COMPATIBILITY MATRIX The plugin compatibility matrix is the following: Page 4
  • 5. Systems where it has been tested • SUSE Linux Enterprise Server 11 (x86_64) • Outlook Web Access 14.355.2 Systems where it should work • SUSE Linux Enterprise Server 11 (x86_64) or higher • Outlook Web Access 14.355.2 or higher It is posible that, due to changes in the login process, some changes in the plugin would be necessary in the Outlook Web Acess. 4 DOCUMENTATION PROVIDED BY THE REQUESTING AREA The requesting area must send the following information: • Domain in which Outlook Web Access is installed. Page 5
  • 6. • Data from 5 users to perform the monitoring: ◦ User domain ◦ Username ◦ Password • If an error detection is required the area must provide a list with the errors to monitor. 5 MODULES PROVIDED BY THE PLUGIN The plugin can perform three kind of checks: login test, index test and error checking. • The index test checks if the services is accessible loading the index page. • The login test checks whether or not is possible to login into the application. • The error tests could be used together with index and login checks and look for the error Page 6
  • 7. passed during the index and login tests. 6 REQUIREMENTS For the correct work of the plugin, this software should be installed: • Pandora FMS 3.2.1 Server or higher • Perl Libraries: Page 7
  • 9. 7 INSTALLING To install the plugin, you will only have to copy it in a folder of the server, and after this register it as a plugin in the plugin management Pandora Console section. The configuration of the plugin register will be like this: Page 9
  • 10. 8 MONITORING CONFIGURATION 8.1. Plugin Parameters The plugin configuration parameters are the following: • check_owa.sh --domain <domain> --check <check_type> --users_file <users_file> [-- error_str <error_string>] • domain: Domain where the OWA server is installed. • check: Check type, that could be: ◦ index: checks that it is possible to have access to the OWA welcome form. ◦ login: checks tht login using several users. • user_file: file that contains the user credentials to test the login. • error_str: (optional) checks if an specific error string is shown while navigation. It is posible to use regular expressions. An example that shows that it is checking the login is: ./check_owa.pl --domain "my.exchange.com" --check login --users_file users.txt To check an error string we write: ./check_owa.pl --domain "my.exchange.com" --check login --users_file users.txt --error_str 403 8.2. users.txt File Format This file has the credentials of the multiple users that are authorized to check that the login form works correctly. The file format is the following: DOMAINuser1;password1 DOMAINuser2;password2 DOMAINuser3;password3 DOMAINuser4;password4 The best option is to use 5 users, because more makes the plugin execution slower. The reason of using only 5 users is to avoid false positives if the accounts are blocked. For this reason, checks will be always be done in base to the number of users of the file. Page 10
  • 11. 8.3. Creating a Plugin module This plugin has to be registered in Pandora as server plugin. When creating a module that uses this plugin it will be necessary to put all the parameters in the Plug-in parameters field, for example: P l u g - i n p a r a m e t e r s : - - d o m a i n m y d o m a i n . c o m – c h e c k l o g i n – u s e r s _ f i l e /var/www/html/pandora_console/plugin/users2.txt –error_str 500 Page 11