Module: nagvis Branch: master Commit: d4c0c7c12db6ccabacc21d67c6c8ad5c3909442a URL: http://nagvis.git.sourceforge.net/git/gitweb.cgi?p=nagvis/nagvis;a=commit;h=d4c0c7c12db6ccabacc21d67c6c8ad5c3909442a
Author: LaMi <[email protected]> Date: Sat Dec 19 14:13:29 2009 +0100 Added first docs for new AA --- docs/en_US/auth.html | 19 +++++++++++++++++++ docs/en_US/auth_old_style.html | 17 +++++++++++++++++ docs/en_US/toc.html | 12 ++++++++---- 3 files changed, 44 insertions(+), 4 deletions(-) diff --git a/docs/en_US/auth.html b/docs/en_US/auth.html new file mode 100644 index 0000000..fd95b53 --- /dev/null +++ b/docs/en_US/auth.html @@ -0,0 +1,19 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> +<html> +<head> + <link rel="stylesheet" type="text/css" media="screen" href="../general/css/style.css" /> + <title>Authentication / Autorization</title> +</head> +<body> + <h1>Authentication / Autorization (AA)</h1> +<p>In the versions prior to 1.5 NagVis didn't care much about the authentication and autorization. In the most environments NagVis used the basic authentication provided by Nagios. This was a side effect of that NagVis was placed in the <code>nagios/share</code> directory. +<p>In NagVis 1.5 the default installation directory has been moved to an own base directory. With this step a new Authentication and Autorization mechanism has been created. The main focus on this concept is to be modular and flexible.</p> +<h2>Modularity</h2> +<p>The AA has been splitted up in three module bases: LogonDialogs, Authentication, Autorization. All modules can be changed without affecting the others.</p> +<h2>Default Modules</h2> +<p>By default NagVis uses a HTML form for logging on users and a SQLite database for storing users, passwords and permissions. Therefor it uses the HTML logon dialog (FrontendModLogonDialog), the SQLite authentication (CoreAuthModSQLite) and the SQLite autorization (CoreAuthorisationModSQLite) modules.</p> +<h2>Other Modules</h2> +<p>On delivery there are only the above authentication and autorisation modules available. Having such a modular structure it should be easy to create LDAP, MySQL, file based authentication and autorisation mechanism. By default NagVis uses the HTML logon dialog for requesting authentication informations from the user. It is possible to add own logon modules for serving other dialogs or ways of logging in.</p> +<p>It is also possible to realize a "trusted" authentication mechanism. NagVis uses the configured environment variable to identify the user. This way the user is not really authenticated with NagVis. NagVis trusts the provided username blindly. You can add several authentication mechanism to your webserver, started from the basic authentication used by Nagios (.htaccess) to single sign on environments. Simply set logonmodule to "LogonEnv", put the environment variable to use as username to the option logonenvvar and tell the authentication module to create users in the database when provided users does not exist.</p> +</body> +</html> diff --git a/docs/en_US/auth_old_style.html b/docs/en_US/auth_old_style.html new file mode 100644 index 0000000..2daa3f1 --- /dev/null +++ b/docs/en_US/auth_old_style.html @@ -0,0 +1,17 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> +<html> +<head> + <link rel="stylesheet" type="text/css" media="screen" href="../general/css/style.css" /> + <title>Authentication / Autorization</title> +</head> +<body> + <h1>Old Style Authentication</h1> +<p>In the versions prior to 1.5 NagVis didn't care much about the authentication and autorization. In the most environments NagVis used the basic authentication provided by Nagios. This was a side effect of that NagVis was placed in the <code>nagios/share</code> directory. +<p>In NagVis 1.5 the default installation directory has been moved to an own base directory. With this step a new Authentication and Autorization mechanism has been created. The main focus on this concept is to be modular and flexible.</p> +<p>If you really like to use the basic authentication provided by Nagios you may use the LogonEnv module to set up a trusted authentication. To make this possible simply set the following options in the <code>[global]</code> section in the NagVis main configuration file:</p> +<pre>logonmodule="LogonEnv" +logonenvvar="REMOTE_USER" +logonenvcreateuser="1"</pre> +These lines tell NagVis to use the LogonEnv module which reads the authenticated user from an environment variable. The second parameter tells the LogonEnv module which variable to use for reading the users name. The third option tells the LogonEnv module to create unknown users in the NagVis AA database. +</body> +</html> diff --git a/docs/en_US/toc.html b/docs/en_US/toc.html index 39e66fc..d7cc08f 100644 --- a/docs/en_US/toc.html +++ b/docs/en_US/toc.html @@ -35,10 +35,14 @@ <dd><a href="map_config_format_description.html" target="Main"><strong>Map configuration</strong></a></dd> <dd><a href="automap_config_format.html" target="Main"><strong>Automap configuration</strong></a></dd> + <dt><br /><strong>Authentication/Autorisation</strong></dt> + <dd><a href="auth.html" target="Main"><strong>General</strong></a> <font style="color:#ff0000;">*</font></dd> + <dd><a href="auth_old_style.html" target="Main"><strong>Old style Auth</strong></a> <font style="color:#ff0000;">*</font></dd> + <dt><br /><strong>Advanced</strong></dt> - <dd><a href="backends.html" target="Main"><strong>Backends</strong></a> <font style="color:#ff0000;">*</font></dd> - <dd><a href="gadgets.html" target="Main"><strong>Gadgets</strong></a> <font style="color:#ff0000;">*</font></dd> - <dd><a href="context_templates.html" target="Main"><strong>Context Templates</strong></a> <font style="color:#ff0000;">*</font></dd> + <dd><a href="backends.html" target="Main"><strong>Backends</strong></a></dd> + <dd><a href="gadgets.html" target="Main"><strong>Gadgets</strong></a></dd> + <dd><a href="context_templates.html" target="Main"><strong>Context Templates</strong></a></dd> <dd><a href="header_templates.html" target="Main"><strong>Header Templates</strong></a></dd> <dd><a href="hover_templates.html" target="Main"><strong>Hover Templates</strong></a></dd> @@ -49,7 +53,7 @@ <dd><a href="extending/templates.html" target="Main"><strong>Install Templates</strong></a></dd> <dd><a href="extending/custom_context_actions.html" target="Main"><strong>Custom Context Actions</strong></a> <font style="color:#ff0000;">*</font></dd> </dl> - <p><font style="color:#ff0000;">*</font>) New in 1.4</p> + <p><font style="color:#ff0000;">*</font>) New in 1.5</p> <div style="text-align:center;margin-top:20px;"> <p><a href="http://www.nagvis.org"; style="margin: 0px;" class="nostyle"><img width="88" height="23" border="0" alt="NagVis Logo" src="../general/img/logo-88x23.png" style="margin: 0px;" /></a></p> <p><a href="http://sourceforge.net"; style="margin: 0px;" class="nostyle"><img width="88" height="31" border="0" alt="SourceForge.net Logo" src="http://sflogo.sourceforge.net/sflogo.php?group_id=132019&type=1"; style="margin: 0px;" /></a></p> ------------------------------------------------------------------------------ This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev _______________________________________________ Nagvis-checkins mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/nagvis-checkins
